v-0.1 (alpha quality) gwsmhg is available for download at ...
Peter Williams
pwil3058 at bigpond.net.au
Mon May 25 00:50:35 CDT 2009
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).
I thought about modifying gquilt to handle this process but as it is a
front end to both quilt and mq this would have been both messy and
difficult. So I decided to make a tool where hg and mq control were
integrated in order to get the best out of mq. The "Workspace Update"
menu inside gwsmhg's MQ notebook page provides the means for a step by
step application of the process described in Section 12.8 above with the
addition of a QPush(merge) button in the MQ tool bar to facilitate
merging patches one at a time (for use by chickens like me who find
"qpush -m -a" a bit scary when there are a large number of patches with
potential merge problems).
> I've also been
> looking for a tool that manages patch imports, etc.
Personally, I prefer to use MQ to merge patches in an orderly fashion
(rather than using "hg import") but will probably add a button or menu
item to invoke "hg import" into gwsmhg at some stage. The current
version of gwsmhg is just a starting point and more functionality will
be added over time. For hg commands that I don't use very much myself
the problem of what is the best way to provide a graphical interface to
them tends to slow me down. For commands I use a lot I just do what
makes their use easiest for me :-).
> So I may indeed
> include gwsmhg in later TortoiseHG installers.
I was thinking that I might add a menu to gwsmhg for invoking TortoiseHg
tools using hgtk. I think that both ideas have merit and aren't
mutually exclusive.
Peter
--
Peter Williams pwil3058 at bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
More information about the Mercurial-devel
mailing list