From: Ian Jackson <iwj@xenproject.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
"xen-devel\@lists.xenproject.org"
<xen-devel@lists.xenproject.org>
Subject: Re: Ping: [PATCH] docs: release-technician-checklist: update to leaf tree version pinning
Date: Mon, 7 Jun 2021 12:14:46 +0100 [thread overview]
Message-ID: <24765.65446.517292.529623@mariner.uk.xensource.com> (raw)
In-Reply-To: <41f6ae32-4704-a580-f103-9e1e9e51330f@suse.com>
Jan Beulich writes ("Re: Ping: [PATCH] docs: release-technician-checklist: update to leaf tree version pinning"):
> On 27.04.2021 18:01, Jan Beulich wrote:
> > On 07.04.2021 11:56, Jan Beulich wrote:
> >> Our releases look to flip-flop between keeping or discarding the date
> >> and title of the referenced qemu-trad commit. I think with the hash
> >> replaced by a tag, the commit's date and title would better also be
> >> purged.
> >>
> >> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> >> ---
> >> I've been noticing this inconsistency repeatedly because I simply re-use
> >> version update patches for the stable trees - the context mismatch
> >> results in a such updated patch to then not apply, due to said flip-
> >> flopping. For 4.15 I'm inclined to drop the two offending lines perhaps
> >> while updating the version to 4.15.1-pre.
> >
> > Ian (and others), any thoughts here either way?
>
> If I don't hear back by Wednesday, I guess I'll take the lazy consensus
> route and put this in.
That would of course be correct of you :-).
But I should explicitly:
Acked-by: Ian Jackson <iwj@xenproject.org>
Thanks,
Ian.
prev parent reply other threads:[~2021-06-07 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 9:56 [PATCH] docs: release-technician-checklist: update to leaf tree version pinning Jan Beulich
2021-04-27 16:01 ` Ping: " Jan Beulich
2021-06-07 10:27 ` Jan Beulich
2021-06-07 11:14 ` Ian Jackson [this message]
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=24765.65446.517292.529623@mariner.uk.xensource.com \
--to=iwj@xenproject.org \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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;
as well as URLs for NNTP newsgroup(s).