Bug? "hg fetch" updates before merge

[Ted Pavlic]

In my opinion, "hg fetch" should...

1. hg pull

2. IF NO NEW HEAD, THEN hg update

3. IF NEW HEAD, THEN hg merge && hg commit

However, right now it appears like "hg fetch" is doing

1. hg pull

2. hg update

3. IF NEW HEAD, THEN hg merge && hg commit

In this case, step #2 may update the working directory to the PULLed 
tip. Hence, anything in the working directory that isn't in the remote 
repository is blown away and then put BACK by the merge in step 3. I 
can't stand this behavior because it causes everything in my working 
directory to get touched after I fetch a few small changes from another 
repo that doesn't include my working files.

Why does "hg fetch" do an update even though a merge is coming?

--Ted

-- 
Ted Pavlic <ted at tedpavlic.com>

   Please visit my ALS association page:
         http://web.alsa.org/goto/tedpavlic
   My family appreciates your support in the fight to defeat ALS.