On Sun, 06 Mar 2011 00:54:39 +1100, Tim Delaney firstname.lastname@example.org wrote:
If those were to be removed from .hgignore then there would be a high likelihood of someone doing "hg addremove" and inadvertently tracking them. The purpose of .hgignore is to prevent inadventently tracking files that shouldn't be tracked.
Ah, well, I don't like that UI. The purpose for me of .hgignore (and similar ignore files) is to make the status command show any files that have been modified or aren't normal build/run products. I'd rather add and remove files individually by hand (except when adding or removing a directory). I also want a --strict option for the commit command that refuses to commit if there are unignored unadded or missing files. (--strict is the bzr spelling; I don't care about the spelling :)
"hg status -i" will list all ignored files that are present in your working directory. For other options, "hg help status".
hg status -i is useless because there are a *lot* of ignored files in a working directory where python has been built. I'd have to do a distclean first, which would mean I'd have to do a rebuild after...and all of that just takes too long :)
I guess I have some hg hacking in my future, unless someone has already written extensions for this stuff.
-- R. David Murray www.bitdance.com