All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.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: Fri, 22 Feb 2008 11:03:50 -0800	[thread overview]
Message-ID: <47BF1C96.1060100@goop.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0802220827520.19896@woody.linux-foundation.org>

Linus Torvalds wrote:
> This isn't a problem with things like "Signed-off-by:" etc tags, because 
> they have no automated meaning and don't really change the commit itself, 
> but the "From:"/"Date:"/"Subject:" markers at the head of the message 
> really do have real meaning, and get removed from the commit message and 
> instead get put into the SCM headers.
>   

It may be worth having a definitive and unambiguous Author: tag then, 
which can appear among Signed-off-by:s and is used in preference to 
anything else.  From: is a useful heuristic which seems to work well in 
general, but as you say, it gets a bit hairy when you have something 
which means different things to different parts of the software stack at 
the same time.

    J

      reply	other threads:[~2008-02-22 19:06 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
2008-02-22 12:18       ` Andi Kleen
2008-02-22 16:43         ` Linus Torvalds
2008-02-22 19:03           ` Jeremy Fitzhardinge [this message]

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=47BF1C96.1060100@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.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.