[ANN] TortoiseHg 1.0.1

[Yuki KODAMA]

On Fri, Apr 2, 2010 at 13:04, Steve Borho <steve at borho.org> wrote:
> On Thu, Apr 1, 2010 at 10:58 PM, Steve Borho <steve at borho.org> wrote:
>> On Thu, Apr 1, 2010 at 10:39 PM, Yuki KODAMA <endflow.net at gmail.com> wrote:
>>> On Fri, Apr 2, 2010 at 10:45, Steve Borho <steve at borho.org> wrote:
>>>> TortoiseHg 1.0.1 is a bug fix release.  We recommend all users upgrade
>>>> to this release.
>>>>
>>>> http://bitbucket.org/tortoisehg/stable/wiki/ReleaseNotes
>>>>
>>>> http://tortoisehg.bitbucket.org/download/index.html
>>>>
>>>> Be aware that the older (<=0.9.3) uninstallers have a tendency to
>>>> delete your user Mercurial.ini file.  We recommend you make a copy of
>>>> it before uninstalling the older TortoiseHg.
>>>>
>>>> --
>>>> Steve Borho
>>>> _______________________________________________
>>>> Mercurial mailing list
>>>> Mercurial at selenic.com
>>>> http://selenic.com/mailman/listinfo/mercurial
>>>>
>>>
>>> I installed 1.0.1 to Windows XP 32-bit box.
>>> But the installer appends "C:\Program Files\TortoiseHg\" to PATH
>>> environment variable,
>>> not "C:\Program Files\TortoiseHg".  As a result, we can't use "hg"
>>> command via Windows
>>> command prompt.
>>
>> I have the same in my PATH on Vista, but the command line tools work.
>> I guess Vista is more forgiving.
>
> Somewhat more importantly, can Mercurial find TortoisePlink and kdiff
> in that PATH?
> The easiest way to test would be to fire up the settings tool and look
> at the merge tools.
>
> --
> Steve Borho
>

Sorry Steve, I couldn't reproduce this issue.
"hg" and other tools can be used via command prompt.
I installed some "hg" version for testing.
So when I saw "hg version" result (1.5), I misunderstood that 1.5.1
doesn't work.
Even if the installer appends unneeded backslashes, it works well.

-- 
Yuki KODAMA