From: Fam Zheng <famz@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PULL 6/6] README: Document 'git-publish' workflow
Date: Mon, 5 Mar 2018 20:23:14 +0800 [thread overview]
Message-ID: <20180305122314.GA13252@lemon.usersys.redhat.com> (raw)
In-Reply-To: <w51bmg24wxs.fsf@maestria.local.igalia.com>
On Mon, 03/05 11:51, Alberto Garcia wrote:
> On Mon 05 Mar 2018 10:40:06 AM CET, Stefan Hajnoczi wrote:
> > +A 'git-profile' utility was created to make above process less
> > +cumbersome, and is highly recommended for making regular
> > contributions,
>
> A 'git-profile' utility ? Did you want to say 'git-publish' there?
Oops. Apparently, yes.
Fam
next prev parent reply other threads:[~2018-03-05 12:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 9:40 [Qemu-devel] [PULL 0/6] Block patches Stefan Hajnoczi
2018-03-05 9:40 ` [Qemu-devel] [PULL 1/6] util/uri.c: Coding style check, Only whitespace involved Stefan Hajnoczi
2018-03-05 9:40 ` [Qemu-devel] [PULL 2/6] util/uri.c: remove brackets that wrap `return` statement's content Stefan Hajnoczi
2018-03-05 9:40 ` [Qemu-devel] [PULL 3/6] util/uri.c: wrap single statement blocks with braces {} Stefan Hajnoczi
2018-03-05 9:40 ` [Qemu-devel] [PULL 4/6] tests/libqos: Check for valid dev pointer when looking for PCI devices Stefan Hajnoczi
2018-03-05 9:40 ` [Qemu-devel] [PULL 5/6] Add a git-publish configuration file Stefan Hajnoczi
2018-03-05 9:40 ` [Qemu-devel] [PULL 6/6] README: Document 'git-publish' workflow Stefan Hajnoczi
2018-03-05 10:51 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-03-05 12:23 ` Fam Zheng [this message]
2018-03-05 9:52 ` [Qemu-devel] [PULL 0/6] Block patches no-reply
2018-03-05 18:55 ` Peter Maydell
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=20180305122314.GA13252@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=berto@igalia.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).