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: Wed, 27 Sep 2006 10:05:03 +0200 [thread overview]
Message-ID: <4d8e3fd30609270105pee59188p8043dda694878e36@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609261439220.3952@g5.osdl.org>
On 9/26/06, Linus Torvalds <torvalds@osdl.org> wrote:
> On Tue, 26 Sep 2006, Paolo Ciarrocchi wrote:
> >
> > out of curiosity, wouldn't be better to sync with Andrew via git?
> > Why via plain patches?
> >
> > What am I missing?
>
> I think you're just missing that we've become so used to it that it's just
> easier than all the alternatives.
Umh.. good point ;)
> Also, the way we do things with Andrew actually has a few advantages over
> a straight git-to-git merge. In particular, when Andrew sends me his
> current stable quilt queue, every email is also Cc'd to the people who
> sent it to him originally or were otherwise involved.
I forgot that Andrew is CC'ing the "author" of the patch when he sends
to you the email.
> So the very act of transferring the patches from one tree to another
> sometimes produces an extra acknowledgement cycle, and we've had patches
> that got NACK'ed at that point because it was an older version of the
> patch etc.
>
> Now, I suspect this is more of an advantage with Andrew's tree than with
> most other trees (most other trees tend to have a much stricter focus),
> and perhaps equally importantly, it also wouldn't really work very well if
> _everybody_ did it, so I personally believe this is one of those
> situations where what's good for _one_ case may not actually be wonderful
> for _all_ cases.
>
> I think it's worked out pretty well, no?
Oh yes! I just did the mistake to think that the work flow of Andrew
was similar to the one used by Andy. And that's clearly a mistake.
Thanks for the clarification.
Ciao,
--
Paolo
http://paolo.ciarrocchi.googlepages.com
http://picasaweb.google.com/paolo.ciarrocchi
next prev parent reply other threads:[~2006-09-27 8:05 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
2006-09-26 21:43 ` Linus Torvalds
2006-09-27 7:44 ` Rolf Eike Beer
2006-09-27 8:05 ` Paolo Ciarrocchi [this message]
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=4d8e3fd30609270105pee59188p8043dda694878e36@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®