Re: Some ideas for StGIT

From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
Date: Aug 4, 2007, 21:35 UTC
Message-ID: <20070804213549.GA1967@filer.fsl.cs.sunysb.edu>
In-Reply-To: <20070804063858.GA13758@thunk.org>

On Sat, Aug 04, 2007 at 02:38:58AM -0400, Theodore Tso wrote:

Show 12 quoted lines

> On Fri, Aug 03, 2007 at 01:50:10PM -0400, Pavel Roskin wrote:
> > Hello!
> > 
> > I was recently disappointed to learn that one of the Linux drivers
> > (bcm43xx_mac80211, to be precise) switched from git to quilt.  I asked
> > whether StGIT was considered, a discussion followed, and I think the key
> > points need to be shared with StGIT developers.  I'll add some of my
> > ideas to the mix.
> 
> You might also ask them if they considered "guilt", which uses
> text-based patches.  It's a lot easier to use, and if they really want
> quilt-like functionality, "guilt" will provide it.

 
I guess I should chime in.

The goal behind guilt is to be very simple yet powerful enough to do what is necessary to maintain a piece of kernel code (read: to scratch my own itch).

> And because it's so stupid simple, it's much rarer that something goes
> seriously wrong that requires me to use a recovery procedure in the
> first place.

Thanks! :)

Show 6 quoted lines

> Editing patch headers are also a lot easier with guilt; you can just
> go ahead and edit them all, and then you can fresh them in git by
> doing a "guilt pop -a; guilt push -a".  Since it's not using a
> git-based storage, it doesn't have to rewrite the whole patch stack
> when you modify a single patch header; you can edit a whole bunch of
> text headers and then refresh the git commit series just once.

FYI: v0.27 allows you to edit the patch headers with: guilt header -e

Pavel, if you have any questions, you know where to ask :)

Josef 'Jeff' Sipek.

-- 
Don't drink and derive. Alcohol and algebra don't mix.