From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Cc: "John W. Linville" <linville@tuxdriver.com>,
David Miller <davem@davemloft.net>,
sfr@canb.auug.org.au, akpm@linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: New GIT net tree naming...
Date: Thu, 8 May 2008 09:06:29 +0200 [thread overview]
Message-ID: <200805080906.29603.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <20080508014358.GE3412@tuxdriver.com>
> For changes against Linus's current tree:
...
> For development meant to be merged in the next merge
> window we have:
Is this relevant for us, the patch submitters? Or should we
continue to create patches against wireless-testing?
next prev parent reply other threads:[~2008-05-08 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080419.173510.257216556.davem@davemloft.net>
2008-05-08 1:43 ` New GIT net tree naming John W. Linville
2008-05-08 7:06 ` Holger Schurig [this message]
2008-05-08 14:40 ` John W. Linville
2008-05-12 17:39 ` Tomas Winkler
2008-05-12 18:47 ` John W. Linville
2008-05-13 10:05 ` Tomas Winkler
2008-05-13 13:26 ` John W. Linville
2008-05-08 7:42 ` Stephen Rothwell
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=200805080906.29603.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).