v-0.1 (alpha quality) gwsmhg is available for download at ...

[Peter Williams]

Peter Arrenbrecht wrote:
> On Mon, May 25, 2009 at 7:50 AM, Peter Williams <pwil3058 at bigpond.net.au> wrote:
>> Steve Borho wrote:
>>> [bits deleted]
>>>
>>> It's our long-term goal to support MQ in a decent fashion, and your
>>> tool looks like it would cover that very nicely.
>> Truth be told this was the main instigator for gwsmhg.  I'm the author of
>> gquilt which started out as a PyGTK wrapper around the quilt scripts which I
>> used to use for maintaining Linux kernel patches.  Then somebody asked could
>> it be used with mq so I built a mq back end for it.  I found that I liked mq
>> better than quilt and in particular I liked the help that it gave in
>> updating patches to a new version of the underlying code (as described in
>> 12.8 "Updating your patches when the underlying code changes" of the
>> Mercurial Manual).
> 
> If your patches are longer lived, you might want to take a look at
> pbranch, which manages patches as diffs between regular Mercurial
> branches. Makes rebasing onto newer underlying code and such even more
> controlled.
> 
>   http://arrenbrecht.ch/mercurial/pbranch
> 
> Wouldn't it be nice if this bought me a GUI for pbranch. ;)

I've had a brief look at this and my immediate reaction is that it needs 
at least two more commands in order for a GUI wrapper to be possible. 
Namely, a command to report the name of the current patch branch and 
another to give a list of the available patch branches.

Peter
-- 
Peter Williams                                   pwil3058 at bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce