Re: StGIT vs. guilt: What's the difference?

From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
Date: Jun 17, 2007, 03:59 UTC
Message-ID: <20070617035923.GI7025@filer.fsl.cs.sunysb.edu>
In-Reply-To: <20070615200139.GS6992@nan92-1-81-57-214-146.fbx.proxad.net>

On Fri, Jun 15, 2007 at 10:01:39PM +0200, Yann Dirson wrote:

> On Fri, Jun 15, 2007 at 03:59:24PM +0100, Catalin Marinas wrote:

...

Show 6 quoted lines

> However, storing diffs is certainly a great way to interact with
> legacy SCMs, and there are situations where guilt is certainly more
> suited than stgit.  Eg, on a project where you have to use CVS, and
> you have to maintain changes to a Linux kernel, and you want to store
> the history of a series of patches, guilt will be much easier to use
> than stgit.

Then there is the psychological effect. If I have a directory full of patch(1) compatible diff files, I can forget about guilt and just use the diff files directly. With stgit's way of storing the patches, I'd assume things can get a bit harder if you just want to give up on stgit.

Btw, does git-prune & friends do the right thing and not destroy the patch-related objects?

...

Show 6 quoted lines

> Well, people may not like python, but IMHO it is a lot easier to learn
> it if you don't know it (that's what I did, although I did not start
> from zero), than writing a robust and maintainable software of even
> moderate complexity in shell script.  Shell script may be good for
> prototyping or gluing tools in a simple way, but for advanced sofware
> on which to rely to store my own data, it is just not really suited.

So, why do you use git? ;)

Josef "Jeff" Sipek.

-- 
The box said "Windows XP or better required". So I installed Linux.