From: Bill Davidsen <davidsen@tmr.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.12-rc6
Date: Mon, 06 Jun 2005 17:54:31 -0400 [thread overview]
Message-ID: <42A4C617.8030404@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0506061407520.1876@ppc970.osdl.org>
Linus Torvalds wrote:
>
> On Mon, 6 Jun 2005, Pavel Machek wrote:
>
>>Linus, perhaps your scripts are doing something wrong? They should
>>have taken From in the description; or did I provide wrong changelog?
>
>
> My scripts definitely do the expected thing.
>
> In git, the author is always in the fixed header, and you never look for
> it anywhere else. However, in order for the author to _get_ there in the
> first place, the person who commits the thing needs to haev the author
> info.
>
> In this case it was me, and I get the author information from the email
> when I commit an emailed patch. I take it from the first line of the body
> if that one is a valid "From:" line, and otherwise I fall back to taking
> it from the headers of the email.
>
> So in this case you got tagged, either because the patch came through
> Andrew (it has his sign-off) and _he_ sent the email but incorrectly had
> you as the "From:" person, or alternatively because you sent the email and
> took Andrew's sign-off but didn't put the "From:" in the right spot.
Any process which only works when multiple people do everything
correctly is not going to be robust. Perhaps you want to use the first
"signed-off-by" line or some such, rather than relying on mail headers?
next prev parent reply other threads:[~2005-06-06 21:54 UTC|newest]
Thread overview: 41+ 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 [this message]
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
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 16:20 ` 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=42A4C617.8030404@tmr.com \
--to=davidsen@tmr.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox