From: Michael Wu <flamingice@sourmilk.net>
To: "John W. Linville" <linville@tuxdriver.com>
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 09:20:07 -0500 [thread overview]
Message-ID: <200612040920.11583.flamingice@sourmilk.net> (raw)
In-Reply-To: <20061204125139.GA10912@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On Monday 04 December 2006 07:51, John W. Linville wrote:
> 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.
>
Sure.
> 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).
>
I will keep separate branches for each driver then.
> It is not my intent to scold (so please don't feel scolded). It just
> is counter-productive to prematurely consolidate merging duties.
>
No problem. It seemed like a good idea for zd1211rw, so I was offering to do
the same for other drivers.
Thanks,
-Michael Wu
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-12-04 14:20 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
2006-12-04 14:03 ` Daniel Drake
2006-12-04 14:20 ` Michael Wu [this message]
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=200612040920.11583.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=dsd@gentoo.org \
--cc=kune@deine-taler.de \
--cc=linville@tuxdriver.com \
--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).