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]
Date:	Tue, 26 Sep 2006 15:20:33 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Sam Ravnborg <sam@...nborg.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 Wed, 27 Sep 2006, Sam Ravnborg wrote:

> On Tue, Sep 26, 2006 at 01:44:42PM -0700, Linus Torvalds wrote:
> >
> > 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.

Yeah, I won't argue against that too much. I'm a pure git user myself, 
although my patterns tend to be different from most other people (only 
fairly small code changes, and mostly merging other peoples code: I end up 
often touching source code more when I do some trivial manual conflict 
resolution than at most other times..)

And yes, making "git diff" as efficient as possible was definitely one of 
the things that I worked on, exactly because it is how I work when I do 
end up working on something: continually reminding myself what the other 
changes I did were..

So "git" should work fine for pretty much any normal development, but a 
patch maintenance system it ain't.

			Linus
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ