hgmerge on Windows - small bug
Matt Mackall
mpm at selenic.com
Tue Feb 5 10:24:01 CST 2008
[cc:ing to list]
On Tue, 2008-02-05 at 10:46 -0500, Alexis Dorais-Joncas wrote:
> Just wanted to point out that in this version of hg :
>
> C:\temp>hg --version
> Mercurial Distributed SCM (version 83d193a513c8+20080204)
...
> When a hgmerge.cmd script exists in a system path that contains spaces
> (i.e. "c:\Program files\mercurial\hgmerge.cmd"), the script does not get
> called :
> [...]
> merging kwm/CommunicationManager.cs
> 'C:\Program' is not recognized as an internal or external command,
> operable program or batch file.
> merging kwm/CommunicationManager.cs failed!
>
> However, when I put the hgmerge.cmd script in c:\windows\system32 (which
> also is in the system path), things run OK.
Yep, that was spotted and fixed yesterday, I just pushed the fix out
now.
> I also want to offer you my help to test windows-specific stuff. Is
> there any particular mailing list I should subscribe to in order to see
> when something in particular needs Windows testing ?
Indeed there is!
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial
mailing list