From: Junio C Hamano <junio@pobox.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xen: Implement getgeo for Xen virtual block device.
Date: Thu, 21 Feb 2008 14:46:36 -0800 [thread overview]
Message-ID: <7vodaarkqb.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <47BDF151.30809@goop.org> (Jeremy Fitzhardinge's message of "Thu, 21 Feb 2008 13:46:57 -0800")
Jeremy Fitzhardinge <jeremy@goop.org> writes:
> Putting the From: in the Signed-off-by block is a result of two thoughts:
>
> 1. putting it at the top makes the most sense from an email
> perspective, but it often seem to get lost by various
> patch-posting programs if it gets tangled in the Subject/summary
> part of the patch. The result is that it needs to float in an odd
> way:
>
> Subject: wooble the foo
>
> From: Foo Woobler <foo@wooble.com>
>
> Wooble foos in the appropriate manner.
>
> Signed-off-by: Foo Woobler <foo@wooble.com>
> Cc: Bar Mangler <bar@mangle.org>
>
> 2. There's already a block of email addresses which describe how
> people relate to this patch,...
In addition to "From: ", you can place "Subject: " and "Date: "
at the beginning to make sure Linus or whoever applies patches
would not get the authorship information from the e-mail itself
you send (this is especially true when you are forwarding
somebody else's patch).
Mnemonic is that the equivalents to E-mail headers go at the
top. You will never have Signed-off-by:, Tested-by:, nor
Acked-by: in your e-mail headers. They go at the bottom.
This is just a toolsmith speaking, I am not in any way
trying to set a policy for this list.
I do not know where that Cc: near S-o-b: comes from, though. It
is not accepted at the top as there is no place for such an
information in commits.
next prev parent reply other threads:[~2008-02-21 22:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 21:03 [PATCH] xen: Implement getgeo for Xen virtual block device Jeremy Fitzhardinge
2008-02-21 21:16 ` Linus Torvalds
2008-02-21 21:17 ` Jeremy Fitzhardinge
2008-02-21 21:38 ` Linus Torvalds
2008-02-21 21:46 ` Jeremy Fitzhardinge
2008-02-21 22:46 ` Junio C Hamano [this message]
2008-02-22 12:18 ` Andi Kleen
2008-02-22 16:43 ` Linus Torvalds
2008-02-22 19:03 ` Jeremy Fitzhardinge
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=7vodaarkqb.fsf@gitster.siamese.dyndns.org \
--to=junio@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.