hg purge purges files in .ignore
solo turn
soloturn at gmail.com
Wed Jun 6 04:51:07 UTC 2007
On 6/4/07, Alexis S. L. Carvalho <alexis at cecm.usp.br> wrote:
> Thus spake solo turn:
> > on windows "hg purge" purges files which are in .hgignore. this is
> > very inconsistent and unexpected. as the name "hgignore" says, these
> > files should (must) be ignored by hg. and purge belongs to hg.
>
> I guess this depends on why you added the file to .hgignore - files
> autogenerated by the build system (*.o) are probably more than ok to
> purge, but if you're versioning parts of your $HOME and told hg to
> ignore the rest, things could get really ugly...
why? to tell mercurial to ignore these files in "set commands", i.e.
where you do not specify the exact filename.
use case: use one directory for committing to cvs and mercurial, so
there are CVS and a .hg. revert leaves us with .origs, and purge is
comfortable to remove these, but leaves us without CVS :)
> We should add some options to purge to remove only
> unknown/ignored/directories. Not sure what the default should be (we
> already have a --print as a "don't do anything flag").
we do "hg status", see some files and then "hg purge" and a completely
different file set is concerned. therefor i'd prefer respecting
.hgignore the default.
files autogenerated by the build system can be purged by the clean
systems clean command, no need for mercurial.
-solo
More information about the Mercurial
mailing list