From: Yi Li <lovelylich@gmail.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Difference between Net and Net-Next
Date: Thu, 28 Mar 2013 16:06:27 +0800 [thread overview]
Message-ID: <5153FA03.6010005@gmail.com> (raw)
In-Reply-To: <20130328062814.GC2511@netboy.at.omicron.at>
于 2013年03月28日 14:28, Richard Cochran 写道:
> On Wed, Mar 27, 2013 at 05:02:28PM +0000, Jim Baxter wrote:
>> How do you decide which changes should go into "net" and which ones go into "net-
>> next"?
>>
>> At a guess I would think bug fixes are in "net" and feature changes into
>> "net-next" but it is not obvious from the commit log.
> I'll go out on a limb and try to explain this:
>
> net-next - changes for the next merge window
> net - bug fixes and cleanups for the current release candidate
>
> HTR (hope thats right),
> Richard
>
net-next - new features added in development and *experimental*
net - features(thought as steady and come frome net-next tree) and bug
fixes, can be merged into linux.git(which is the tree below) by Linus.
linux - the mainline release.
That's my opinion.
regards,
Yi
next prev parent reply other threads:[~2013-03-28 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 17:02 Difference between Net and Net-Next Jim Baxter
2013-03-28 6:28 ` Richard Cochran
2013-03-28 8:06 ` Yi Li [this message]
2013-03-28 12:52 ` Jim Baxter
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=5153FA03.6010005@gmail.com \
--to=lovelylich@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
/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).