netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: David Shwatrz <dshwatrz@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: A short question about net git tree and patches
Date: Thu, 20 Dec 2007 10:55:10 +0100	[thread overview]
Message-ID: <20071220095510.GA2081@uranus.ravnborg.org> (raw)
In-Reply-To: <31436f4a0712200120o4e6de008jf999ca1024b47f9d@mail.gmail.com>

On Thu, Dec 20, 2007 at 11:20:26AM +0200, David Shwatrz wrote:
> Hello,
> I have a short question regarding the net git tree and patches:
> I want to write and send patches against the most recent and
> bleeding edge kernel networking code.
> I see in:
> http://kernel.org/pub/scm/linux/kernel/git/davem/?C=M;O=A
> that there are 3 git trees which can be candidates for git-clone and
> making patches against;
> these are:
> netdev-2.6.git, net-2.6.25.git and net-2.6.git.
> 
> It seems to me that net-2.6.git is the most suitable one to work against;
> am I right ?
> what is the difference, in short, between the three repositories?

IIRC the usage is:
netdev-2.6.git   <= old stuff, 4 weeks since last update. Not in use
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.

	Sam

  reply	other threads:[~2007-12-20  9:53 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 [this message]
2007-12-20 10:49   ` Ilpo Järvinen
2007-12-20 11:22   ` David Miller
2007-12-20 13:39     ` Sam Ravnborg

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=20071220095510.GA2081@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --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).