[issue761] tracking clones on the same mapped network drive (windows)

[Thomas Gay]

New submission from Thomas Gay <tom at yagmot.com>:

there appears to be a problem tracking clones located on the same mapped network
drive.

testing procedure:
on mapped network drive z:\
created dir "original" and initialized. created a file, added the file, committed.
cloned "original" to "testClone"
made changes to the file in "original" and committed.
hg log shows the same output in "original" and "testClone"

on mapped network drive z:\
created dir "repo1" and initialized. created a file, added the file, committed.
created dir "repo2" and initialized. created a file, added the file, committed.
made changes to the file in "repo1" and committed.
hg log shows the expected differences

on local drive c:\
created dir "original" and initialized. created a file, added the file, committed.
cloned "original" to "testClone"
made changes to the file in "original" and committed.
hg log shows the expected differences

on mapped network drive z:\
created dir "original" and initialized. created a file, added the file, committed.
cloned "original" to another mapped network drive "w:\testClone"
made changes to the file in "original" and committed.
hg log shows the expected differences

----------
messages: 4068
nosy: aychseven
priority: bug
status: unread
title: tracking clones on the same mapped network drive (windows)
topic: windows

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