From: Jiri Pirko <jpirko@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] net: correct a comment for the final #endif
Date: Thu, 28 May 2009 09:05:36 +0200 [thread overview]
Message-ID: <20090528070535.GA21538@psychotron.englab.brq.redhat.com> (raw)
In-Reply-To: <4A1E31A7.6090905@gmail.com>
Thu, May 28, 2009 at 08:39:35AM CEST, eric.dumazet@gmail.com wrote:
>David Miller a écrit :
>> From: Jiri Pirko <jpirko@redhat.com>
>> Date: Thu, 28 May 2009 07:47:13 +0200
>>
>>> Btw how do you choose what patch to apply to what tree?
>>
>> It depends upon where we are in the development cycle and the
>> nature of your patch.
>>
>> Right now we're only applying the most critical bug fixes
>> to net-2.6, anything else goes to net-next-2.6
>>
>
>I append here some extra stuff
>
>net-2.6 is the tree for pending patches for Linus, for the about to be
>released version (2.6.30 as today)
>
>As the merge window (for 2.6.30) is now closed, only bug fixes are allowed.
>
>For cleanups, and new network stuff (possibly introducing new bugs),
>net-next-2.6 is the right tree. This gives time for various testers
>to discover bugs so we can fix them before hitting public release.
>
>When Linus releases 2.6.30, opening merge window of one week, then all patches
>pending in net-next-2.6 will take their way to Linus tree for 2.6.31
>
>Some exceptions are allowed, but this is the general idea.
>
>Hope this helps
Fine, thanks you both guys.
>
prev parent reply other threads:[~2009-05-28 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 14:01 [PATCH] net: correct a comment for the final #endif Jiri Pirko
2009-05-27 22:49 ` David Miller
2009-05-28 5:47 ` Jiri Pirko
2009-05-28 6:33 ` David Miller
2009-05-28 6:39 ` Eric Dumazet
2009-05-28 7:05 ` Jiri Pirko [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=20090528070535.GA21538@psychotron.englab.brq.redhat.com \
--to=jpirko@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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).