linux-kernel - Re: x86/x86-64 merge for 2.6.19

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060926220457.GA12905@uranus.ravnborg.org>
Date:	Wed, 27 Sep 2006 00:04:57 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org,
	discuss@...-64.org
Subject: Re: x86/x86-64 merge for 2.6.19

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/