From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, rpjday@crashcourse.ca
Subject: Re: + netdev-cassini-use-shorter-list_splice_init-macro-for-brevity.patch added to -mm tree
Date: Mon, 24 Mar 2008 16:48:10 -0700 (PDT) [thread overview]
Message-ID: <20080324.164810.83653077.davem@davemloft.net> (raw)
In-Reply-To: <20080324163105.154a031a.akpm@linux-foundation.org>
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.
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 :-)
next prev parent reply other threads:[~2008-03-24 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 22:31 + netdev-cassini-use-shorter-list_splice_init-macro-for-brevity.patch added to -mm tree akpm
2008-03-24 22:56 ` David Miller
2008-03-24 23:10 ` Andrew Morton
2008-03-24 23:21 ` David Miller
2008-03-24 23:31 ` Andrew Morton
2008-03-24 23:48 ` David Miller [this message]
2008-03-25 0:00 ` Andrew Morton
2008-03-25 0:14 ` David Miller
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=20080324.164810.83653077.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.