On Thu, Dec 20, 2007 at 03:22:58AM -0800, David Miller wrote:
> From: Sam Ravnborg <[EMAIL PROTECTED]>
> 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
> >
From: Sam Ravnborg <[EMAIL PROTECTED]>
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 co
On Thu, 20 Dec 2007, Sam Ravnborg wrote:
> 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
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/d
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-cl
