linux-kernel - Re: [git patches] net driver updates for .27

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080612.152214.21877307.davem@davemloft.net>
Date:	Thu, 12 Jun 2008 15:22:14 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jeff@...zik.org
Cc:	sfr@...b.auug.org.au, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [git patches] net driver updates for .27

From: Jeff Garzik <jeff@...zik.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@...b.auug.org.au>
> Date:   Thu May 29 22:39:28 2008 +1000
> 
>      [netdrvr] Fix 8390 build breakage
> 
>      From: tony@...eyournoodle.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.

"Author" is always who wrote the patch, and I think it's important to
be consistent in that area.

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? :-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/