ANN: __hg_ps1

Greg Ward greg-hg at gerg.ca
Sat Apr 18 07:50:17 CDT 2009


[me, on vcprompt]
> Oh good!  The goal of vcprompt is to be as lightweight as possible.
> Never mind counting how many processes or Python interpreters I start;
> I was counting system calls.  Certainly for the initial phase, "am I
> even in a VC working dir, and if so is it CVS, Git, Mercurial, ...?"
> that kind of paranoia is justified.

[Pierre]
> What do you do if it's all three?  Just curious.

First one wins.  Default test order is CVS, Git, Mercurial.  It's not
customizable, but should be.  When/if I add Subversion support, it'll
come right after CVS. Rationale: they are more widely used, *and* it's
far more likely that someone will layer a temporary private git/hg/bzr
repo on top of a CVS/Subversion working dir than the other way around.
 In such a case, the underlying CVS/Subversion working dir is "more
important", in the sense that the branch you're committing to there is
the one that will affect your peers.  If I screw up my local temporary
git/hg/bzr repo, only I am affected.

Greg


More information about the Mercurial mailing list