public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:08:23 -0400	[thread overview]
Message-ID: <48519E57.3030906@garzik.org> (raw)
In-Reply-To: <20080611.212929.71729484.davem@davemloft.net>

David Miller wrote:
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Thu, 12 Jun 2008 13:38:42 +1000
> 
>> Hi Jeff,
>>
>> On Wed, 11 Jun 2008 22:30:46 -0400 Jeff Garzik <jeff@garzik.org> wrote:
>>> Stephen Rothwell (1):
>>>       [netdrvr] Fix 8390 build breakage
>> That patch is actually from Tony Breeds ..
> 
> Jeff, there is still time to fix this.  If you want, just
> fix up that patch in your tree to get the attribution
> and author field correct, and send me a new pull request.

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)

     ...

     Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
     Signed-off-by: Jeff Garzik <jgarzik@redhat.com>


It's pretty hard to miss, and it accurately captures the entire audit trail:

1) who sent the patch?
2) who wrote the patch?
3) who committed the patch?

So, you want to eliminate part of that audit trail (#1), making the 
commit audit trail more hidden and opaque?

I respectfully disagree.  We should capture the _entire_ audit trail, 
not hide bits of it.

Full credit is given, as you can see from looking at the commit.

	Jeff




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

Thread overview: 26+ 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 [this message]
2008-06-12 22:22       ` David Miller
2008-06-12 22:43         ` Jeff Garzik
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
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=48519E57.3030906@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