"hg ct" vs "hgct"

[Alexandre Fayolle]

On Mon, Jun 19, 2006 at 10:08:27AM +0100, Mark Williamson wrote:
> > > If that one problem were fixed, I'd be much happier.
> >
> > A consequence of this is the weird behaviour of commit tool (hg ct) when
> > run from  a directory which is not the root : it displays the changed
> > files, but fails to show the diffs because it lacks information about
> > relative paths.
> 
> Does that happen if you use the "hg ct" command (the ct extension) rather than 
> running hgct directly?

You're right. 
 
> I thought the extension cd-ed to the root of the repository before running 
> hgct in order to avoid this.

OK. On the other hand, I prefer using "hgct" to "hg ct", because the
latter exits after each commit, while the former enables be to perform
several commits in a row, on different files, without relaunching the
command.  

-- 
Alexandre Fayolle                              LOGILAB, Paris (France)
Formations Python, Zope, Plone, Debian:  http://www.logilab.fr/formations
Développement logiciel sur mesure:       http://www.logilab.fr/services
Informatique scientifique:               http://www.logilab.fr/science
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: Digital signature
Url : http://www.selenic.com/pipermail/mercurial/attachments/20060619/1135b1be/attachment.pgp