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

From: Catalin Marinas <catalin.marinas@gmail.com>
Date: Jun 17, 2007, 08:54 UTC
Message-ID: <b0943d9e0706170154v75603612qe85bbc4d8f2b2049@mail.gmail.com>
In-Reply-To: <20070617035923.GI7025@filer.fsl.cs.sunysb.edu>

On 17/06/07, Josef Sipek <jsipek@fsl.cs.sunysb.edu> wrote:

> 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.

I do this a lot to refine patches but I export the patch and re-import it (I can even merge it with the old version using 'stg fold --threeway' and it will prompt me for the differences via xxdiff or emacs).

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

StGIT patches are git-prune safe. The commit ids are stored in .git/refs/patches.

Show 8 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? ;)

Well, I guess he's mostly using StGIT which uses only the built-in GIT commands written in C :-).

-- 
Catalin