mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: alan@lxorguk.ukuu.org.uk, greg@kroah.com, sfr@canb.auug.org.au,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: is the weeks before -rc1 the time to really be working on -next?
Date: Wed, 15 Oct 2008 16:08:21 -0700 (PDT)	[thread overview]
Message-ID: <20081015.160821.143702739.davem@davemloft.net> (raw)
In-Reply-To: <20081015155353.f15a996e.akpm@linux-foundation.org>

From: Andrew Morton <akpm@linux-foundation.org>
Date: Wed, 15 Oct 2008 15:53:53 -0700

> But the problem here is that once linux-next merges your patches, you
> no longer have a tree on which to base your patches!  You need to get
> your hands on "linux-next without my stuff" to maintain them.

I know this doesn't work for you, but if you ran -mm just like any
other GIT tree it might mesh a whole lot better.

And in reality that kind of situation isn't a big deal in the
context of -next.  People are rebasing their trees all the time
there, and it mostly seems to work itself out.

It's a lot more work for a contributor to do work against -mm,
since the response to "which -mm should I work against and where
do I get it from" is a bit more involved that just "pull from
this GIT tree and do your work on top of that."

And just like networking we could have Stephen treat the -mm
GIT tree as "important" which roughly means that other conflicting
trees will be knocked out of a -next release in deference to -mm.

Those people will have to fix their stuff, not you.  And you'll
always therefore get coverage in -next.

Unlike the general sentiment expressed here, I think -next is helping.
Even if only because Stephen pokes people with trees causing problems
on a daily basis.

  reply	other threads:[~2008-10-15 23:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 17:40 Greg KH
2008-10-15 20:04 ` Geert Uytterhoeven
2008-10-15 20:30   ` Greg KH
2008-10-15 21:56 ` Andrew Morton
2008-10-15 22:08   ` Rafael J. Wysocki
2008-10-15 22:36   ` Alan Cox
2008-10-15 22:53     ` Andrew Morton
2008-10-15 23:08       ` David Miller [this message]
2008-10-15 23:41         ` Andrew Morton
2008-10-15 23:53           ` Tony Luck
2008-10-15 23:56           ` 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=20081015.160821.143702739.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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

all inboxes | Powered by JetHome®