"staging area"?

[Daniel Carrera]

On Sun, Jun 20, 2010 at 8:34 PM, Masklinn <masklinn at masklinn.net> wrote:
[snip]
> As you can see, if you commit when the file is in a "missing" state (!, assuming you have
> other changes to commit) a coworker seeing the commited revision will *still* have the
> file because as far as mercurial is concerned it's still there. If you commit when the file is
> in R state, then from this revision onwards (and unless you reintroduce it) the file
> doesn't exist anymore in the repository.

Ohhhhhhh....

Thanks for the explanation, and the code example. So I really do want
to run "hg rm" always.

Ok, new question: Is there any reason why someone would *not* want to
run "hg rm"? If the point of revision control is to propagate changes
and track history, why wouldn't everyone wan to run "hg rm"?

Daniel.
-- 
No trees were killed in the generation of this message. A large number
of electrons were, however, severely inconvenienced.