From: "John W. Linville" <linville@tuxdriver.com>
To: bruno randolf <bruno@thinktube.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Upstream wireless process changes
Date: Mon, 18 Feb 2008 10:27:35 -0500 [thread overview]
Message-ID: <20080218152735.GA3098@tuxdriver.com> (raw)
In-Reply-To: <200802181129.14291.bruno@thinktube.com>
On Mon, Feb 18, 2008 at 11:29:14AM +0900, bruno randolf wrote:
> On Friday 15 February 2008 07:57:28 John W. Linville wrote:
> > Finally, a new wireless-testing tree will be created to replace the
> > usage of the former 'everything' branch. This tree will be based
> this might be a stupid question, but which tree do you expect us to base
> regular development patches on? i basically don't really care when my patches
> are merged upstream, and i don't know enough about upstream processes to
> decide that, so i think i'll better leave that decision up to you :)
I guess I wasn't as clear as I thought I was... :-)
Please use wireless-testing as your primary development target.
Thanks!
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2008-02-18 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 22:57 Upstream wireless process changes John W. Linville
2008-02-18 2:29 ` bruno randolf
2008-02-18 15:27 ` John W. Linville [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=20080218152735.GA3098@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bruno@thinktube.com \
--cc=linux-wireless@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).