From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 13:46:57 -0800 [thread overview]
Message-ID: <47BDF151.30809@goop.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0802211337220.19896@woody.linux-foundation.org>
Linus Torvalds wrote:
> On Thu, 21 Feb 2008, Jeremy Fitzhardinge wrote:
>
>> OK. Have you fixed it, or shall I resend?
>>
>
> I'll fix it, but I want people to know so that I don't have to fix things
> like this in the future (*).
>
> Linus
>
> (*) I keed, I keed. Of *course* I'll have to fix things like this in the
> future too. But hopefully not quite as often.
>
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, so why not put From: there (since it
isn't really an email From header, but a patch metadata header).
I'd assumed that tools which pick "Thing: Email" pairs out of a
patch would deal with From in the same place as a Signed-off-by.
After all, tools deal with Cc:s there.
I'll make sure From: is in the right place in future, but I just wanted
to point out it wasn't complete randomness.
J
next prev parent reply other threads:[~2008-02-21 21:49 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 [this message]
2008-02-21 22:46 ` Junio C Hamano
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=47BDF151.30809@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.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.