All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Pavel Machek <pavel@suse.cz>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.12-rc6
Date: Mon, 6 Jun 2005 23:07:31 +0100	[thread overview]
Message-ID: <20050606230730.C12034@flint.arm.linux.org.uk> (raw)
In-Reply-To: <9a87484905060614576c09d08d@mail.gmail.com>; from jesper.juhl@gmail.com on Mon, Jun 06, 2005 at 11:57:00PM +0200

On Mon, Jun 06, 2005 at 11:57:00PM +0200, Jesper Juhl wrote:
> On 6/6/05, Linus Torvalds <torvalds@osdl.org> wrote:
> > 
> > 
> > On Mon, 6 Jun 2005, Pavel Machek wrote:
> > >
> > > There is "From: Dmitry..." in the changelog. Do your script move first
> > > "From:" into author header and delete it from changelog? That would
> > > explain it...
> > 
> > Yes. But note how it doesn't even take the "first" From: line, it
> > literally takes the From: line _only_ if that line is the first line in
> > the email body.
> > 
> 
> A lot of times I see mails getting forwarded to you/Andrew/other
> maintainer by someone without adding a From: or other indication of
> who was the original author, but in almost all cases the original
> author is the one listed as the first Signed-off-by: since authors are
> the first to sign off on a patch, so, wouldn't it make more sense to
> pick the author like this ;

Not necessarily.  Re-read what Signed-off-by: is all about and who
may provide that line.  You should find that the first Signed-off-by:
line may not be the author themselves, but someone else who is able
to satisfy our requirements.

I think people will just have to accept that there's no way to _always_
_automatically_ get the proper author for every patch. (and that calling
it author in git was probably the first mistake - we never had these
issues with BK which didn't specifically indentify anything as being
the "author" as such.)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-06-06 22:08 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06 18:08 Linux v2.6.12-rc6 Linus Torvalds
2005-06-06 19:26 ` Pavel Machek
2005-06-06 19:54   ` Jeff Garzik
2005-06-06 20:05     ` Pavel Machek
2005-06-06 21:11       ` Linus Torvalds
2005-06-06 21:54         ` Bill Davidsen
2005-06-06 20:12   ` Linus Torvalds
2005-06-06 20:14     ` Pavel Machek
2005-06-06 21:13       ` Linus Torvalds
2005-06-06 21:18         ` Pavel Machek
2005-06-06 21:36           ` Linus Torvalds
2005-06-06 21:41             ` Pavel Machek
2005-06-06 21:53               ` Linus Torvalds
2005-06-06 21:57         ` Jesper Juhl
2005-06-06 22:07           ` Russell King [this message]
2005-06-07  9:11 ` Johannes Stezenbach
2005-06-08 11:15   ` Johannes Stezenbach
2005-06-08 11:23     ` Brice Goglin
2005-06-08 11:37       ` Johannes Stezenbach
2005-06-17 17:48         ` Bill Davidsen
2005-06-18 13:57           ` Johannes Stezenbach
2005-06-18 17:10             ` Johannes Stezenbach
2005-06-07 13:05 ` Erik Mouw
2005-06-07 15:28   ` Linus Torvalds
2005-06-07 17:11     ` Erik Mouw
2005-06-07 17:28       ` Linus Torvalds
2005-06-08  2:08     ` Paul Mackerras
2005-06-08 17:11       ` Linus Torvalds
2005-06-08 23:16       ` gitk (was Re: Linux v2.6.12-rc6) Linus Torvalds
2005-06-10 10:57         ` Paul Mackerras
2005-06-08 16:20     ` Linux v2.6.12-rc6 Nicolas Pitre
2005-06-07 18:47 ` Jean Delvare
2005-06-09  8:10   ` Greg KH
2005-06-09 15:52     ` Jean Delvare
2005-06-09 16:32       ` Greg KH
2005-06-08 13:37 ` segfaults suddenly appearing Jakob Oestergaard
  -- strict thread matches above, loose matches on Subject: below --
2005-06-07  6:11 Linux v2.6.12-rc6 Voluspa
2005-06-07  6:18 ` Ingo Molnar
2005-06-07  6:37   ` Voluspa
2005-06-07  7:06     ` Grant Coady
2005-06-07  7:44       ` Dave Airlie
2005-06-07  8:45         ` Voluspa
2005-06-07  8:19     ` Matthias Andree

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=20050606230730.C12034@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=torvalds@osdl.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.