a bug with "hg update"

Zhikai Cheng zhikai.cheng at garmin.com
Fri Jan 18 15:06:26 CST 2008


Hello,

the Mercurial is a good tool I really like it and enjoyed to use it.
I wish it get better.

I did the following with Mercurial:

1) I run the following command:
hg mv file.1 file.2

(file.1 is an existing file in the Mercurial repository.)

Then, a new file file.2 was created as expected, and the file.1 was
renamed as file.1.orig.

2) before I tried to compile all my source code for testing
I run the 1) hg pull and 2) hg update.

3) After step 2 I found that : the file.1.orig was renamed as file.1


I could not understand why this occurred.   since that file.1.orig has
different name with file.1 and its time stamp is later than the file.1
in the repository. 

The file.1.orig should not be replaced with file.1 after run the hg
update.

Any comments or explanations?

Thanks,

Zhikai


------------------------- 
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient.  If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited.  If you have received this e-mail in error, please contact the sender and delete all copies. 
Thank you for your cooperation 



More information about the Mercurial mailing list