<div class="h5">
</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Explorer of Windows 7 has indeed the same problem as Vista.<br>
<br>
Mercurial already worked around this problem of Explorer by introducing<br>
a new repo format with version 1.7 (dotencode format) which encodes<br>
leading spaces inside .hg/store.<br>
<br>
Look into the file .hg/requires in your repo. If it contains<br>
<br>
revlogv1<br>
store<br>
fncache<br>
dotencode<br>
<br>
then the repo is using the current latest format which is resilient<br>
against explorer of Vista and Windows 7 stripping leading spaces of<br>
filenames.<br>
<br>
Upgrading to a newer version of Mercurial will not change the format of<br>
your existing repos. So the best thing for you is using the latest<br>
version of Mercurial and converting your repos to the newest format.<br>
<br>
Conversion happens if you do 'hg clone --pull oldrepo newrepo'.<br>
<br>
See<br>
<a href="http://mercurial.selenic.com/wiki/UpgradingMercurial#Upgrading_and_downgrading_repository_formats" target="_blank">http://mercurial.selenic.com/wiki/UpgradingMercurial#Upgrading_and_downgrading_repository_formats</a><br>
</blockquote></div><br>Useful information! <br><br>I'm at office now, and I have noticed that the leading spaces of file ' _hold option to open a script~c2~8a.i' on this computer still exist, instead of being stripped. So I think if such problem is actually caused between copying repo from Win7 to WindowsXP. <br>
<br>Office computer installed TortoiseHg 1.0 and Mercurial 1.5, which I just used to get my current repo by cloning from a remote server, and when I tried to verify it today, all goes well. It means that though I have used the latest version of TortoiseHg and Mercurial on my home computer, but the repo has been corrupted when copying from office. In other words, Win7(32bit version) would not do auto-stripping though filename contains leading spaces, but when copying repo to WindowsXP, leading spaces will be stripped, thus repo corruption problem occurs. <br>
<br>So according to Adrian's important suggestion and my today's finding, I think there maybe two solutions for me:<br>1) convert the repo on my home computer with --pull cloning<br>But the repo has already been currpted, so I'm not sure the files which has been stripped will be recoveried after conversion. <br>
If it's ok, then good. If not, I think I can hack the fncache file.<br><br>2) import my changesets to office computer and try to push <br>Because repo on office computer is not corrupted, so it's ok to import these new changesets, the only troublesome thing is remaking changes and recommitting them.<br>
<br><br>That's all I can think and summary; hope it can help someone who have the same problem in future.<br><br>Best regards,<br>higery<br><br><br>