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: <20061204125139.GA10912@tuxdriver.com>
Date:	Mon, 4 Dec 2006 07:51:45 -0500
From:	"John W. Linville" <linville@...driver.com>
To:	Michael Wu <flamingice@...rmilk.net>
Cc:	Daniel Drake <dsd@...too.org>, Ulrich Kunitz <kune@...ne-taler.de>,
	netdev@...r.kernel.org
Subject: Re: d80211-drivers updated (zd1211rw-d80211 synced with zd1211rw)

On Mon, Dec 04, 2006 at 02:50:39AM -0500, Michael Wu wrote:

> Other (d80211) wireless drivers are welcome 
> to send patches this way if they do not have their own git tree for Linville 
> to pull.

Please don't do this.  It adds to my pain for reviewing patches.

I don't mind (and maybe even like) pulling w/ git from primary driver
authors.  But, I would prefer not to add extra layers of git between
me and the patch authors.

Similarly, I would prefer for Ulrich or Daniel to maintain the zd1211rw
git tree unless you (i.e. Michael) are going to be one of the primary
authors going forward.

While I'm complaining :-), I would probably prefer it if you had
adm8211 and p54 in separate git trees (or at least on separate
branches) as well.  That way, if there is a problem in a p54 patch
series, I can still pull adm8211 (or vice versa).

It is not my intent to scold (so please don't feel scolded).  It just
is counter-productive to prematurely consolidate merging duties.

Thanks,

John
-- 
John W. Linville
linville@...driver.com
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ