mgix at mgix.com
Tue Aug 9 14:18:40 CDT 2005
> And wouldn't be a good option having a new command called "forget" to
> remove the file from being version controlled, and keep "remove" to
> actually remove a file or directory (as its semantics cry for doing)?.
> Having to use an option for a command that you normally would use that
> way is a bad choice, IMHO. Defaults should reflect the most common
> cases and those that make the SCM system as transparent as possible.
> Forgetting a file is something you can eventually do, and could be
> done with an option (or with a command if it's so common), but
> removing a file is definetly something you frequently do, and you mean
> you want to delete it in the working copy and keep it out of the way
> in the repo. Having to do twice the operation because you must inform
> your SCM system is working for this latter, not a convenient use.
Couldn't have said it better myself.
What is your intent when you type hg remove ?
Chances are you want to remove the file.
And you can't.
hg complains it can't remove the file because the file exists.
So your remove it, and then remove it again.
It had better be removed by then.
More information about the Mercurial