Commit Tool for mercurial

[Mark Williamson]

>    I packaged for debian commit-tool, ie (h)gct[1].
> It allows to commit to hg (and git) with a graphical interface.
> The package is available on my web page[2] and will be available in the
> official debian archive once the ftp team approve this new package.

Cool.  There'll be another release in the nearish future with some neat  new 
features in both the UI and the git backend.  We'll let you know...

One thing I've considered doing is calling directly into the hg libraries 
rather than shelling hg commands.  OTOH, this introduces the problems of 
version matching so I'm not keen to do it right now...  (I'm assuming there's 
not going to be a stable library interface to hg for the foreseeable future.)

>    Now, as a mercurial user, it would be great if hgct would be available
> as a mercurial extension, ie called with "hg ct" for example. Is there
> anybody that can do that (I do not know python enough myself).

That's a neat idea.  I'll stick it on my TODO list but if anyone beats me to 
it, they're welcome to it ;-)

>    For (h)gct developpers, it would be useful is this case that hgct
> close itself once the user commited its files. Perhaps an option :
> hgct --one-commit

There's a preferences option to make hgct close when there are no outstanding 
changes.  I guess a one-shot mode would be handy for the mercurial extension 
usage you proposed.

>    As a maintainer, it would be great if mercurial extensions can be
> installed system wide without having to write (and merge) a global
> rc file.
>    What about mercurial reading, for example,  all files in
> /etc/mercurial/hgrc.d/ ? So a mercurial extension can install its
> file in this directory and then all users can use this extension.

I like this idea (but I'm not volunteering this time ;-).

Cheers,
Mark

>    Vincent
>
>
> [1]: http://www.cyd.liu.se/users/~freku045/gct/
> [2]: http://dept-info.labri.fr/~danjean/deb.html#commit-tool