On Mon, 24 Mar 2008 16:48:10 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:

quoted text
> From: Andrew Morton <akpm@linux-foundation.org>
> Date: Mon, 24 Mar 2008 16:31:05 -0700
> 
> > On Mon, 24 Mar 2008 16:21:38 -0700 (PDT)
> > David Miller <davem@davemloft.net> wrote:
> > 
> > > net-2.6.26 is what is going into the linux-next tree
> > 
> > urgh.  I wish I had some algorithm for detecting when net-2.6.x+1 appears.
> > 
> > Perhaps you could create it on the day 2.6.x is released and leave it empty
> > for a while.  That way I'll notice when net-2.6.x vanishes and I can switch
> > to 2.6.x+1 immediately?
> 
> Sure, but in this case you were using plain "net-2.6" which is only
> for bug fixes and is synced fairly rapidly to Linus, so I don't
> see how this is relevant here.

The relevance is that I should have net-2.6.26 in my lineup, but I don't
because I didn't know that it was available, and I didn't think to check.

If I _did_ have net-2.6.26 here, I'd have immediately seen that you'd
already applied this patch.

quoted text
> net-2.6 is always just a sync mechanism, rarely generating merge
> conflicts with other people, and not something people other than say
> Jeff Garzik and John Linville (people who actively push to me) should
> generally follow unless they want to.  It's just the same to follow
> Linus's tree especially as the -rcX process winds down.
> 
> If you had been using net-2.6.24 or something like that, yeah I
> could see the issue :-)

I dropped net-2.6.24 when its git-fetch started failing.  But I have no
automatable way of knowing when to start picking up net-2.6.25.

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/