Will Fiveash wrote: > Why? I ask this because this breaks one of hg status useful features > which is reporting unknown files. And this file is part of the > repository so if I want to change it or remove it in my repository hg > status tells me it's modified/removed and I assume that this will cause > problems with commit/push.
Because nothing else is both accurate and tolerable on a built workspace. The extensive pattern space necessary to properly ignore all of the ON build products drives Mercurial performance to its knees, and the list of ON build products, proto area contents, logs, archives, and packages is long enough to make "hg status -u" output unusable. Anything in between is, to varying degrees, incorrect or intolerable. That said, you may "rm .hgignore," but please don't "hg rm .hgignore." The former will report .hgignore as ! .hgignore ...but a subsequent hg commit will NOT attempt to remove the file. --Mark
