From: Henning Schild <henning.schild@siemens.com>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v4] conf: add new debian version "bookworm"
Date: Mon, 3 Jan 2022 10:51:06 +0100 [thread overview]
Message-ID: <20220103105106.1be17c7d@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <97de58db-1cdb-8e8d-f747-aff71ae18075@siemens.com>
Am Mon, 3 Jan 2022 09:15:47 +0100
schrieb Florian Bezdeka <florian.bezdeka@siemens.com>:
> On 02.01.22 22:27, Henning Schild wrote:
> > |@@ -0,0 +1,7 @@ +# +# Copyright (c) Siemens AG, 2021 +# +#
>
> Happy new year! Shouldn't it be 2022 already? If yes, there are more
> files in this patch that should be revisisted.
Good point, but unless someone insists i will not do that. The roots
are in 2021 ;)
I would also be fine with the maintainer making it 2022 on merge.
Just let me know if i should do a v5 after all.
Henning
> > SPDX-License-Identifier: MIT + +MACHINE ?= "container-amd64"
> > +DISTRO ?= "debian-bookworm"|
>
next prev parent reply other threads:[~2022-01-03 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 21:27 Henning Schild
2022-01-03 8:15 ` Florian Bezdeka
2022-01-03 9:51 ` Henning Schild [this message]
2022-01-14 14:52 ` Anton Mikanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220103105106.1be17c7d@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox