From: Sam Ravnborg <sam@ravnborg.org>
To: David Miller <davem@davemloft.net>
Cc: dshwatrz@gmail.com, netdev@vger.kernel.org
Subject: Re: A short question about net git tree and patches
Date: Thu, 20 Dec 2007 14:39:10 +0100 [thread overview]
Message-ID: <20071220133910.GA3543@uranus.ravnborg.org> (raw)
In-Reply-To: <20071220.032258.265124532.davem@davemloft.net>
On Thu, Dec 20, 2007 at 03:22:58AM -0800, David Miller wrote:
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Thu, 20 Dec 2007 10:55:10 +0100
>
> > net-2.6.25.git <= patches for current kernel release (only fixes)
> > net-2.6.git <= patches for next kernel relase and planned to be
> > applied in next merge window
> >
> > So net-2.6.git is the correct choice for bleeding edge.
>
> You reversed them, net-2.6.25.git is for bleeding edge
> stuff, net-2.6.git is for bug fixes only.
Sorry - thanks for clarifying it.
Sam - who should refrain from thinking too much in current crappy condition
prev parent reply other threads:[~2007-12-20 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 9:20 A short question about net git tree and patches David Shwatrz
2007-12-20 9:55 ` Sam Ravnborg
2007-12-20 10:49 ` Ilpo Järvinen
2007-12-20 11:22 ` David Miller
2007-12-20 13:39 ` Sam Ravnborg [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=20071220133910.GA3543@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davem@davemloft.net \
--cc=dshwatrz@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).