From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: x86/x86-64 merge for 2.6.19
Date: Wed, 27 Sep 2006 00:04:57 +0200 [thread overview]
Message-ID: <20060926220457.GA12905@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0609261339050.3952@g5.osdl.org>
On Tue, Sep 26, 2006 at 01:44:42PM -0700, Linus Torvalds 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.
One of the major benefits from git is that whenever I decide to
do some changes git allows me to start modifying as I like and when
done I just do "git diff | less" to review it. And when it turns out to be a piece of crap I just do "git reset --hard" and be done with it.
This make my life so much easier than having to copy symlinked tress
around all the time - and I then may not touch the base for the symlinks.
Put all other nice and usefull features aside this has been a major
timesaver for me both in the bk days and also now in the git days.
And quilt does not help me in this respect as I understood last I looked.
Using git sometimes does not work out that well for this.
But then I do a simple git format-patch HEAD~nn..HEAD which I apply on top
of a freshly cloned tree and we are back on track. This tricks works for me
since I have only two customers of my kbuild.git tree - akpm and Linus.
Where Linus just pulls into his tree so no problem, and Andrew seems to cope
fine with me doing a fresh tree now and then.
Sam
next prev parent reply other threads:[~2006-09-26 22:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 10:44 x86/x86-64 merge for 2.6.19 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
2006-09-26 22:04 ` Sam Ravnborg [this message]
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=20060926220457.GA12905@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--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