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, 12 Feb 2008 16:49:46 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Greg KH <greg@...ah.com>
cc:	David Miller <davem@...emloft.net>, jeff@...zik.org,
	arjan@...radead.org, sfr@...b.auug.org.au,
	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
	linux-arch@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))



On Tue, 12 Feb 2008, Greg KH wrote:
> 
> Perhaps you need to switch to using quilt.  This is the main reason why
> I use it.

Btw, on that note: if some quilt user can send an "annotated history file" 
of their quilt usage, it's something that git really can do, and I'll see 
if I can merge (or rather, coax Junio to merge) the relevant part of stgit 
to make it possible to just basically get "quilt behaviour" for the parts 
of a git tree that you haven't pushed out yet.

A pure patch-stack will be faster at that thing than git would be (it's 
simply easier to just track patches), but on the other hand, using git 
would get some other advantages outside of the integration issue (eg the 
cherry-pick thing really is a proper three-way merge, not just an "apply 
patch", so it can do better).

It wasn't the original goal of git, but not only are really doing all the 
series management anyway (that is largely what "rebase" is all about, 
after all), but the git goals have obviously expanded over time too. 

			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