From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: takano@axe-inc.co.jp
Cc: Netdev <netdev@vger.kernel.org>, y-kodama@aist.go.jp
Subject: Re: [RFC][PATCH 1/2] TCP: fix lost retransmit detection
Date: Sun, 7 Oct 2007 18:11:44 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710071805380.19695@kivilampi-30.cs.helsinki.fi> (raw)
In-Reply-To: <20071006.231714.41173786.davem@davemloft.net>
...Dropped DaveM from cc, I guess he knows the things I describe below
already... :-)
On Sat, 6 Oct 2007, David Miller wrote:
> From: TAKANO Ryousei <takano@axe-inc.co.jp>
> Date: Sun, 07 Oct 2007 14:51:00 +0900 (JST)
>
> > BTW, what is difference among netdev-2.6,
netdev-2.6 is for network device drivers (stuff under drivers/net)
> net-2.6 (net-2.6.24), and
> > tcp-2.6? I am not familiar with linux kernel development process.
>
> net-2.6.24 tree is current new development
>
> net-2.6 tree is only bug fixes
>
> tcp-2.6 is an old abandonded tree that holds lots of old
> TCP work, most of which is merged already, but one part
> (my RB-Tree SACK patches) are not integrated yet.
In addition, when Linus releases a new kernel (2.6.23), the net-2.6.24
becomes net-2.6 (the old one ceases to exist). At some point of 2.6.24-rc
series, net-2.6.25 gets opened by DaveM, usually it's not available right
after closure of 2.6.24 merge window. ...Then again, the trees are
again rotated when a next official release is made...
--
i.
next prev parent reply other threads:[~2007-10-07 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 9:45 [RFC][PATCH 1/2] TCP: fix lost retransmit detection TAKANO Ryousei
2007-10-05 10:02 ` Ilpo Järvinen
2007-10-07 5:51 ` TAKANO Ryousei
2007-10-07 6:17 ` David Miller
2007-10-07 8:42 ` TAKANO Ryousei
2007-10-07 15:11 ` Ilpo Järvinen [this message]
2007-10-08 11:11 ` Ilpo Järvinen
2007-10-09 6:28 ` TAKANO Ryousei
2007-10-09 12:19 ` Ilpo Järvinen
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=Pine.LNX.4.64.0710071805380.19695@kivilampi-30.cs.helsinki.fi \
--to=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
--cc=takano@axe-inc.co.jp \
--cc=y-kodama@aist.go.jp \
/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).