From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86/x86-64 merge for 2.6.19
Date: Tue, 26 Sep 2006 23:25:19 +0200 [thread overview]
Message-ID: <4d8e3fd30609261425ob262489nec1240f5a0c5050f@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609261339050.3952@g5.osdl.org>
On 9/26/06, Linus Torvalds <torvalds@osdl.org> wrote:
>
>
> On Tue, 26 Sep 2006, Andi Kleen wrote:
> >
> > Yes that is why I did it. I still use quilt for my tree because it works
> > best for me, but together with all the i386 stuff I was over 230 patches
> > and email clearly didn't scale well to that much.
>
> Right. I'm actually surprised not more peole use git that way. It was
> literally one of the _design_goals_ of git to have people use quilt a a
> more "willy-nilly" front-end process, with git giving the true distributed
> nature that you can't get from that kind of softer patch-queue like
> system.
>
> We discussed some quilt integration stuff, but nobody actually ended up
> ever using both (except indirectly, as with the whole Andrew->Linus
> stage). StGit kind of comes closest.
>
> So I don't think your usage should be considered to be even strange. I
> think it makes sense. I just think that everybody agrees that if we can do
> it in chunks of a few tens of patches most of the time instead of chunks
> of 225, everybody will have an easier time, if only because the latency
> goes down, and it's just easier to react.
>
> That said, the merges with Andrew are also sometimes in the 150+ patch
> range, and merging with other git trees can sometimes bring in even more.
Linus,
out of curiosity, wouldn't be better to sync with Andrew via git?
Why via plain patches?
What am I missing?
Thanks.
--
Paolo
http://paolo.ciarrocchi.googlepages.com
http://picasaweb.google.com/paolo.ciarrocchi
next prev parent reply other threads:[~2006-09-26 21:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 10:44 Andi Kleen
2006-09-26 19:48 ` Linus Torvalds
2006-09-26 20:02 ` Andi Kleen
2006-09-26 20:19 ` Linus Torvalds
2006-09-26 20:26 ` Andi Kleen
2006-09-26 20:44 ` Linus Torvalds
2006-09-26 21:23 ` [discuss] " Andi Kleen
2006-09-26 21:39 ` Linus Torvalds
2006-09-26 21:25 ` Paolo Ciarrocchi [this message]
2006-09-26 21:43 ` Linus Torvalds
2006-09-27 7:44 ` Rolf Eike Beer
2006-09-27 8:05 ` Paolo Ciarrocchi
2006-09-26 22:04 ` Sam Ravnborg
2006-09-26 22:20 ` Linus Torvalds
2006-09-27 6:04 ` Jan Engelhardt
2006-09-27 5:41 ` Andrew Morton
2006-09-27 7:11 ` [discuss] " Andi Kleen
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=4d8e3fd30609261425ob262489nec1240f5a0c5050f@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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®