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] [day] [month] [year] [list]

Message-Id: <20080612.161416.82163498.davem@davemloft.net>
Date:	Thu, 12 Jun 2008 16:14:16 -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:43:33 -0400

> David Miller wrote:
> > "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.

I guess that's a compelling enough argument.  I'll pull your
original tree, thanks Jeff.
--
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/