linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Coywolf Qi Hunt <qiyong@fc-cn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: why no -mm git tree?
Date: Tue, 10 Jan 2006 23:18:18 -0800	[thread overview]
Message-ID: <20060110231818.6164dba7.akpm@osdl.org> (raw)
In-Reply-To: <20060111070043.GA7858@localhost.localdomain>

Coywolf Qi Hunt <qiyong@fc-cn.com> wrote:
>
> On Tue, Jan 10, 2006 at 10:44:51PM -0800, Andrew Morton wrote:
> > Coywolf Qi Hunt <qiyong@fc-cn.com> wrote:
> > >
> > > Why don't use a -mm git tree?
> > >
> > 
> > Because everthing would take me 100x longer?
> 
> Really? So does Linus?
> 

Linus does a totally different thing from me.

He reverts about one patch a month.  I drop tens a day.

He never _alters_ patches.  2.6.15-mm1 had about 200 patches which modify
earlier patches and which get rolled up into the patch-which-they-modify
before going upstream.

He never alters the order of patches.

etc.

> > 
> > I'm looking into generating a pullable git tree for each -mm.  Just as a
> > convenience for people who can't type "ftp".
> 
> That doesn't help much if it's only for each -mm.
> If you make git commits for each each patch merged in, then
> we can always run the `current' -mm git tree.

Ah.  If you're suggesting that the -mm git tree have _patches_ under git,
and the way of grabbing the -mm tree is to pull everything and to then
apply all the patches under the patches/ directory then yeah, that would
work.

But my tree at any random point in time is a random piece of
doesn't-even-compile-let-alone-run crap, believe me.  Often not all the
patches even apply.  I don't think there's much point in exposing people to
something like that.


  reply	other threads:[~2006-01-11  7:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11  5:56 why no -mm git tree? Coywolf Qi Hunt
2006-01-11  6:38 ` Jeff Garzik
2006-01-11  6:44 ` Andrew Morton
2006-01-11  7:00   ` Coywolf Qi Hunt
2006-01-11  7:18     ` Andrew Morton [this message]
2006-01-11 12:36       ` Paolo Ciarrocchi
2006-01-11 17:11         ` Andrew Morton
2006-01-12 16:23           ` J. Bruce Fields

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=20060110231818.6164dba7.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiyong@fc-cn.com \
    /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).