From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
Baurzhan Ismagulov <ibr@radix50.net>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3] debianize: Add placeholder for original version to CHANGELOG_V
Date: Fri, 8 May 2020 08:02:05 +0200 [thread overview]
Message-ID: <8d34d89b-c9d8-d83b-61a1-8d8c30d3f721@siemens.com> (raw)
In-Reply-To: <20200507220215.66937111@md1za8fc.ad001.siemens.net>
On 07.05.20 22:02, [ext] Henning Schild wrote:
> Am Thu, 7 May 2020 21:45:02 +0200
> schrieb Baurzhan Ismagulov <ibr@radix50.net>:
>
>> On Thu, Apr 23, 2020 at 06:31:10PM +0200, Jan Kiszka wrote:
>>> This allows to append to the latest upstream version when using an
>>> unpinned source version. The format of the placeholder is
>>> "<orig-version>".
>>
>> Applied to next, thanks.
>
> The discussion was not finished, IMHO.
>
Regarding this patch, we are through IMHO. It makes sense to track at
least stable updates of debian packages, and it will be used for that in
production.
> Jan went for another patch on top "meta-isar: hello: Use <orig-version>
> in CHANGELOG_V" which raised more questions on this series.
>
> The patch on top should have been included in a v4, which would now be
> stuck.
Nope, nothing like that planned.
>
> Not sure how to deal with the premature merge now.
>
Keep it.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-05-08 6:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 16:31 Jan Kiszka
2020-04-23 16:43 ` Henning Schild
2020-04-23 16:50 ` Jan Kiszka
2020-04-23 17:32 ` Henning Schild
2020-04-24 7:59 ` Jan Kiszka
2020-04-23 16:47 ` Henning Schild
2020-05-07 19:45 ` Baurzhan Ismagulov
2020-05-07 20:02 ` Henning Schild
2020-05-07 20:28 ` Baurzhan Ismagulov
2020-05-08 5:45 ` Henning Schild
2020-05-08 6:02 ` Baurzhan Ismagulov
2020-05-08 6:02 ` Jan Kiszka [this message]
2020-05-08 6:06 ` Baurzhan Ismagulov
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=8d34d89b-c9d8-d83b-61a1-8d8c30d3f721@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--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