linux-kernel - Re: [ANNOUNCE] Stacked GIT 0.14.2

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: <b0943d9e0803241640h500e43ffgee55bb9e1b2b04e2@mail.gmail.com>
Date:	Mon, 24 Mar 2008 23:40:04 +0000
From:	"Catalin Marinas" <catalin.marinas@...il.com>
To:	"Rene Herman" <rene.herman@...access.nl>
Cc:	"Junio C Hamano" <gitster@...ox.com>,
	"Jan Engelhardt" <jengelh@...putergmbh.de>,
	git <git@...r.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Josef Sipek" <jsipek@....cs.sunysb.edu>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>
Subject: Re: [ANNOUNCE] Stacked GIT 0.14.2

On 24/03/2008, Rene Herman <rene.herman@...access.nl> wrote:
> used to use quilt and although I
>  didn't much care for its linear nature when managing an entire tree, it
>  probably works out well for private topic branches. Not overly sure of added
>  practical value over git rebase, but I did like the simple nature of
>  shuffling things around by just editing a series file back when I was using
>  quilt. Keeps one on top of things, so to speak (<-- amusing play on words).

Git rebasing is useful but using a patch management tool is much
easier, especially when you need to post a series of patches multiple
times while implementing others' comments. And this is not only for
private branches but public ones that are meant for upstream merging.
The problem with these tools is that they rewrite the history of the
repository but they are OK if you aren't in a position where people
need to base their work on your tree.

I would much prefer to simply commit the additional comments at the
top of a branch without changing the history but this makes patch
posting and reviewing more difficult. Because of this requirement to
keep clean patches (which I think is fair), people using maintainers'
branches can only use rebasing (or some patch management tool).

>  Moreover not too keen on using many tools do do one thing, so getting this
>  inside git itself sounded like a possibly nice notion.

I don't like using many tools either, hence I use mostly StGIT :-).

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