From: Jeff Garzik <jeff@garzik.org>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [git patches] net driver updates for .27
Date: Thu, 12 Jun 2008 18:43:33 -0400 [thread overview]
Message-ID: <4851A695.7050706@garzik.org> (raw)
In-Reply-To: <20080612.152214.21877307.davem@davemloft.net>
David Miller wrote:
> From: Jeff Garzik <jeff@garzik.org>
> Date: Thu, 12 Jun 2008 18:08:23 -0400
>
>> Did you actually read the commit description? It's quite clear who
>> originated the commit:
>>
>>
>> commit 0c1aa20fb87b796d904f4d89ad12e5a0c483127b
>> Author: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Thu May 29 22:39:28 2008 +1000
>>
>> [netdrvr] Fix 8390 build breakage
>>
>> From: tony@bakeyournoodle.com (Tony Breeds)
>
> To each their own, I suppose, but...
>
> If you look at what happens when Andrew dumps a thousand patches to
> Linus this isn't how it is handled.
Sure, Andrew has an alternate method of including himself the audit
trail: adding a signed-off-by line.
sfr didn't do that, and I certainly am not going to add one on his
behalf (and given email mess, the turnaround would have taken a long
time if I had asked via email).
> "Author" is always who wrote the patch, and I think it's important to
> be consistent in that area.
"always"? There are /plenty/ of occasions, usually at big corps, where
the Author is not the person who wrote the patch, but rather the person
who sent the patch.
And you'll note that all Linus's tools capture that -- author is patch
sender -- albeit with optional From parsing from patch commit description.
> Stephen Rothwell isn't the "Author" of this patch any more than you
> are Jeff. By your own logic, you are saying that you could have just
> as equally put yourself in the Author field since hey, you're
> effectively submitting the patch to me via your tree right? :-)
My own logic is merely that we should capture the entire audit trail.
You are welcome to pull netdev-2.6.git#davem-silly if you don't think
the existing pull is sufficient, though.
Jeff
next prev parent reply other threads:[~2008-06-12 22:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 2:30 [git patches] net driver updates for .27 Jeff Garzik
2008-06-12 3:38 ` Stephen Rothwell
2008-06-12 4:29 ` David Miller
2008-06-12 22:08 ` Jeff Garzik
2008-06-12 22:22 ` David Miller
2008-06-12 22:43 ` Jeff Garzik [this message]
2008-06-12 23:14 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-07-11 5:27 Jeff Garzik
2008-07-15 5:36 ` David Miller
2008-07-04 12:54 Jeff Garzik
2008-07-06 4:10 ` David Miller
2008-07-06 4:20 ` David Miller
2008-06-28 15:09 Jeff Garzik
2008-06-29 4:33 ` David Miller
2008-06-27 6:25 Jeff Garzik
2008-06-28 8:39 ` David Miller
2008-06-25 3:15 Jeff Garzik
2008-06-25 4:13 ` Nobuhiro Iwamatsu
2008-06-25 7:20 ` Jeff Garzik
2008-06-25 7:24 ` Nobuhiro Iwamatsu
2008-06-18 4:20 Jeff Garzik
2008-06-18 4:53 ` David Miller
2008-06-02 0:41 Stephen Rothwell
2008-05-22 19:10 Jeff Garzik
[not found] ` <20080522121658.d1523365.akpm@linux-foundation.org>
2008-05-22 19:19 ` Jeff Garzik
2008-05-29 10:33 ` David Miller
2008-05-29 12:39 ` Stephen Rothwell
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=4851A695.7050706@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).