[issue725] can't addremove after replacing symlink with real directory
Dov Feldstern
mercurial-bugs at selenic.com
Tue Sep 4 18:57:53 UTC 2007
New submission from Dov Feldstern <dfeldstern at fastimap.com>:
(version is 0.9.4)
Starting out with a working directory which looks like this:
.
|-- conf
| `-- one
`-- config -> conf
I now do the following:
/tmp/test> rm config
/tmp/test> mkdir config
/tmp/test> echo 1 > config/one
/tmp/test> hg addremove
adding config/one
abort: file named 'config' already in dirstate
It doesn't matter if the symlink originally pointed to a directory or a regular
file. Replacing the symlink with a regular file works fine. It's only replacing
the symlink with a directory which fails.
workaround: hg remove the link, commit; then hg add the new directory in the
next changeset. But doing this sort of beats the whole purpose of having atomic
changesets...
Thanks!
Dov
----------
messages: 3961
nosy: dov
priority: bug
status: unread
title: can't addremove after replacing symlink with real directory
____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue725>
____________________________________________________
More information about the Mercurial-devel
mailing list