[issue612] rename of a directory with built objects causes untracked files to be tracked

Stephen Lau mercurial-bugs at selenic.com
Thu Jun 28 12:21:33 CDT 2007


New submission from Stephen Lau <stevel at sun.com>:

Scenario: Parent has a directory with a source file.  Child takes a clone. 
Child builds the source file (thus creating an object).  Parent renames the
directory.  Child does a 'pull -u', gets the renamed directory.  Mercurial now
thinks it's tracking the previously built object in the new directory name.  'hg
debugstate' shows the object file listed.  If you go into the child's new
directory and rebuild, 'hg status' will show the file as modified and try to
commit it if you do a 'hg commit'

----------
messages: 3398
nosy: stevel
priority: critical
status: unread
title: rename of a directory with built objects causes untracked files to be tracked

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue612>
____________________________________________________



More information about the Mercurial-devel mailing list