From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 0/5] Block patches
Date: Wed, 14 Feb 2018 13:25:08 +0000 [thread overview]
Message-ID: <20180214132508.GA7545@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180214004820.GA15103@lemon.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Wed, Feb 14, 2018 at 08:48:20AM +0800, Fam Zheng wrote:
> On Tue, 02/13 17:34, Stefan Hajnoczi wrote:
> > The following changes since commit fb68096da3d35e64c88cd610c1fa42766c58e92a:
> >
> > Revert "tests: use memfd in vhost-user-test" (2018-02-13 09:51:52 +0000)
> >
> > are available in the Git repository at:
> >
> > git://github.com/stefanha/qemu.git tags/block-pull-request
> >
> > for you to fetch changes up to 64b01feca991e5b19a5d750ef77cdca92b68bdbb:
> >
> > misc: fix spelling (2018-02-13 15:38:17 +0000)
>
> Did you mean "PULL" in the subject?
git-publish is just obeying your profile settings:
+[gitpublishprofile "default"]
+base = master
+prefix = PATCH
^---- :)
I used PULL myself in the past but am happy with using whatever we
decide the standard should be.
Shall we remove prefix from the profiles (it defaults to "PATCH" for
regular patches and "PULL" for pull requests)?
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-02-14 13:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 17:34 [Qemu-devel] [PATCH 0/5] Block patches Stefan Hajnoczi
2018-02-13 17:34 ` [Qemu-devel] [PATCH 1/5] Add a git-publish configuration file Stefan Hajnoczi
2018-02-13 18:09 ` Daniel P. Berrangé
2018-02-14 1:01 ` Fam Zheng
2018-02-14 13:34 ` Stefan Hajnoczi
2018-02-14 13:45 ` Fam Zheng
2018-02-14 15:21 ` Eric Blake
2018-02-14 14:08 ` Paolo Bonzini
2018-02-14 14:27 ` Paolo Bonzini
2018-02-25 6:04 ` Fam Zheng
2018-02-14 17:37 ` Philippe Mathieu-Daudé
2018-02-25 6:05 ` Fam Zheng
2018-02-13 17:34 ` [Qemu-devel] [PATCH 2/5] README: Document 'git-publish' workflow Stefan Hajnoczi
2018-02-13 17:34 ` [Qemu-devel] [PATCH 3/5] vl: pause vcpus before stopping iothreads Stefan Hajnoczi
2018-02-13 17:34 ` [Qemu-devel] [PATCH 4/5] ratelimit: don't align wait time with slices Stefan Hajnoczi
2018-02-13 17:34 ` [Qemu-devel] [PATCH 5/5] misc: fix spelling Stefan Hajnoczi
2018-02-14 0:48 ` [Qemu-devel] [PATCH 0/5] Block patches Fam Zheng
2018-02-14 13:25 ` Stefan Hajnoczi [this message]
2018-02-14 13:58 ` Fam Zheng
2018-02-15 9:39 ` Stefan Hajnoczi
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=20180214132508.GA7545@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).