From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Subject: GIT tree updates...
Date: Sun, 28 Dec 2008 20:06:53 -0800 (PST) [thread overview]
Message-ID: <20081228.200653.129296720.davem@davemloft.net> (raw)
First, I want to thank everyone for all of their hard work on the
changes that went into net-next-2.6
Next, since Linus pulled in my net-next-2.6 tree earlier today I'm
resetting both net-2.6 and net-next-2.6
net-next-2.6 will just be a dumb clone, so that Stephen Rothwell has a
dummy empty tree to pull from for his -next tree. I want to see no
patches meant for 2.6.30 at this time.
net-2.6 is where work will commence, and this means we are only doing
bug fixes and non-intrusive simple cleanups.
If you push the limits of these liberal rules for patches, and we get
burnt by this, you will pay. I am warning everyone now. :-)
reply other threads:[~2008-12-29 4:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081228.200653.129296720.davem@davemloft.net \
--to=davem@davemloft.net \
--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).