From: "John W. Linville" <linville@tuxdriver.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Daniel Drake <dsd@gentoo.org>,
Ulrich Kunitz <kune@deine-taler.de>,
netdev@vger.kernel.org
Subject: Re: d80211-drivers updated (zd1211rw-d80211 synced with zd1211rw)
Date: Mon, 4 Dec 2006 07:51:45 -0500 [thread overview]
Message-ID: <20061204125139.GA10912@tuxdriver.com> (raw)
In-Reply-To: <200612040250.43955.flamingice@sourmilk.net>
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@tuxdriver.com
next prev parent reply other threads:[~2006-12-04 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 7:50 d80211-drivers updated (zd1211rw-d80211 synced with zd1211rw) Michael Wu
2006-12-04 12:51 ` John W. Linville [this message]
2006-12-04 14:03 ` Daniel Drake
2006-12-04 14:20 ` Michael Wu
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=20061204125139.GA10912@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dsd@gentoo.org \
--cc=flamingice@sourmilk.net \
--cc=kune@deine-taler.de \
--cc=netdev@vger.kernel.org \
/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).