3 ms·
> The command addremove is genius. Why? I find that in the middle of a big project I have lots of stupid files strewn about that I absolutely don't want checke
by __david__ 14y ago
> The command addremove is genius.
Why? I find that in the middle of a big project I have lots of stupid files strewn about that I absolutely don't want checked in (TODO lists, patches I'm considering, copies of large log files I'm investigating, etc). I always add things explicitly and delete explicitly, otherwise I'd get random junk checked into my repo. How do you keep your repo clean enough to actually use automatic commands like that?
- koenigdavidmj 14y agoPut that type of thing in .hgignore.
- __david__ 14y agoIsn't that checked in like .gitignore? I'd rather not put stupid local stuff into a file that the rest of the team shares. And if I don't commit it then I'm stuck with a local file that always has changes, which is also begging for trouble. It also implies that I name things in some consistent way or that I add a lot of files into the ignore file. I guess other people just aren't as messy as I am?
- koenigdavidmj 14y agoYou can keep multiple ignore files. Then .hgignore can be shared by the whole team (if you're working in C, you're going to ignore .o files, for instance, and so will everyone else). Look up the ui.ignore hgrc option to add more files (presumably one of which doesn't sync).