From: Eric Blake <eblake@redhat.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch] fix /proc/self/maps output
Date: Fri, 29 Mar 2013 09:18:45 -0600 [thread overview]
Message-ID: <5155B0D5.5080007@redhat.com> (raw)
In-Reply-To: <CAKdteOYy5J9oX3s6Z2GC2n5GQh4hDTBWw24kPTTe3i2P+qgmSA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
On 03/29/2013 09:13 AM, Christophe Lyon wrote:
> Hi,
>
> Sorry I wasn't aware of such restrictions (I'm used to gcc/binutils
> conventions), and my thunderbird does display my patch as if it were
> inline :-)
> So.... trying a cut-and-paste approach in gmail, for this one character patch:
Still not ideal. The commentary above should not be part of the final
commit message, so you should move it...
>
>
> /proc/self/maps: Add a space at end of line when there is no filename
> to print, to conform to linux kernel format.
>
> Signed-off-by: Christophe Lyon <christophe.lyon@linaro.org>
...here, after a --- line that tells 'git am' where to stop reading
commit message. 'git send-email' is your friend. Then whether or not
you use 'git send-email', it is always wise to test if your patch is
usable by first sending it to yourself, and seeing if 'git am' will do
the right thing with it.
http://wiki.qemu.org/Contribute/SubmitAPatch has more hints.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-03-29 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKdteOZ2NHm2eeH72UxahDrPSN5vu46J3ZsjLhFjMYjR=P2R2Q@mail.gmail.com>
2013-03-29 14:33 ` [Qemu-devel] [Patch] fix /proc/self/maps output Christophe Lyon
2013-03-29 14:44 ` Peter Maydell
2013-03-29 15:13 ` Christophe Lyon
2013-03-29 15:18 ` Eric Blake [this message]
2013-03-29 16:01 ` Christophe Lyon
2013-03-29 17:53 ` Peter Maydell
2013-03-29 22:35 ` H. Peter Anvin
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=5155B0D5.5080007@redhat.com \
--to=eblake@redhat.com \
--cc=christophe.lyon@linaro.org \
--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).