From: Fam Zheng <famz@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Howto: instructing patchew about patch dependency
Date: Tue, 8 Aug 2017 22:12:32 +0800 [thread overview]
Message-ID: <20170808141232.GC2454@lemon> (raw)
In-Reply-To: <45317b91-2a3e-3f6e-a0df-1678ee93c97a@redhat.com>
On Tue, 08/08 16:00, Laszlo Ersek wrote:
> On 08/08/17 04:02, Fam Zheng wrote:
> > Hi, QEMU patch submitters,
> >
> > I've patched patchew so that if you add a line:
> >
> > Based-on: $MESSAGE_ID
> >
> > in your cover letter body, or in a reply to it (or reply to reply), patchew will
> > try to apply your series on top of the one $MESSAGE_ID refers to, assuming the
> > base series _was_ successfully applied by patchew earlier.
> >
> > In the single patch case, you can put the line under the "---" mark in the
> > commit message (no need to let it enter git history).
> >
> > For human readability, around the "Based-on:" line it may be better if the
> > subject is noted. E.g.:
> >
> > Based-on: 20170804140942.19342-1-famz@redhat.com
> > ([PATCH for-2.10] vmdk: Fix error handling/reporting of vmdk_check)
> >
> > Please don't join them in one line because it will confuse the parser, after all
> > following the message id text, there aren't many spaces left.
>
> If the basis is a multi-patch series, should Based-on refer to the msgid
> of the last patch in that series, or its blurb? (I guess "refer to
> blurb" is more logical, but asking shouldn't hurt.)
My bad for not making it clear: patchew identifies patch series by cover letter
message id, so yes, "blurb" is right.
Fam
prev parent reply other threads:[~2017-08-08 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 2:02 [Qemu-devel] Howto: instructing patchew about patch dependency Fam Zheng
2017-08-08 12:43 ` Peter Maydell
2017-08-08 13:59 ` Fam Zheng
2017-08-08 14:00 ` Laszlo Ersek
2017-08-08 14:12 ` Fam Zheng [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=20170808141232.GC2454@lemon \
--to=famz@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.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).