Mercurial Digest, Vol 28, Issue 41

[Brian Baker]

> First of all, responding to a rude comment with a rude comment of
your
> own rarely helps your position. 

Fair comment.

> Second, I'm actually not sure what it
> is that you want hg add to do... I started using mercurial about 3
> months ago and have never been surprised by any functionality,
> including hg add. Everything worked exactly as I expected it to. If
> you read the documentation you should have no surprises.
> Third, what do you mean by default behavior? Using hg add with no
> parameters? Yes, I use that constantly. I don't think I've ever had
to
> specify a parameter when doing hg add. Run hg status to see what is
> about to happen then run hg add or hg addremove to get your files in
> and/or out of the repository. If you don't want something added,
> create hgignore rules.

Due to working practices beyond my control I want to be able to use
mercurial in a 'lightweight' way. I've got a big source tree with lots
of files, and I want to version control just the ones that I edit.
These files are spread fairly sparsely through the large tree, I add
each file that I edit.

hg add with no arguments adds everything 
there isn't an unadd command
One typo and its a headache to tidy up.

I appreciate that this isn't the 'normal' way of using Mercurial. 
However, the fact that the add command default behaviour can cause wide
ranging changes that can't be readily undone says to me that perhaps
the interface should be reconsidered.

With CVS at least you can manually edit the files used to manage the
repository to unadd files before a commit.

Brian



      ___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/