From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, akpm@linux-foundation.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: New GIT net tree naming...
Date: Wed, 7 May 2008 21:43:58 -0400 [thread overview]
Message-ID: <20080508014358.GE3412@tuxdriver.com> (raw)
In-Reply-To: <20080419.173510.257216556.davem@davemloft.net>
On Sat, Apr 19, 2008 at 05:35:10PM -0700, David Miller wrote:
>
> Based upon feedback from Andrew and others I'm now starting
> to use a new naming scheme for my GIT trees:
>
> For changes against Linus's current tree:
>
> master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git
>
> For development meant to be merged in the next merge
> window we have:
>
> master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git
>
> Andrew/Stephen, let me know if this works for you. This way
> the tree names will never change.
I have adopted this same scheme for wireless as well:
For changes against Linus's current tree:
master.kernel.org:/pub/scm/linux/kernel/git/linville/wireless-2.6.git
For development meant to be merged in the next merge
window we have:
master.kernel.org:/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git
John
--
John W. Linville
linville@tuxdriver.com
next parent reply other threads:[~2008-05-08 1:59 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 ` John W. Linville [this message]
2008-05-08 7:06 ` New GIT net tree naming Holger Schurig
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=20080508014358.GE3412@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.