hgeol and TortoiseHg clone?

[Kurt Granroth]

On 7/23/10 2:47 AM, Martin Geisler wrote:
> Kurt Granroth<kurt.mercurial at granroth.com>  writes:
>
>> On 7/22/10 1:47 PM, Martin Geisler wrote:
>>> Kurt Granroth<kurt.mercurial at granroth.com>   writes:
>>>
>>> It should really "just work" (tm)
>>
>> Okay.  That actually helps quite a bit knowing that it's *supposed* to
>> work exactly like that... meaning there is something odd about my
>> specific setup.
>>
>> Curiously, when I run tests Linux->Linux with the local hgrc have
>> eol.native = CRLF (to simulate Windows), it always works great!
>
> Thanks -- it helps me to know that this setup works. As you might have
> guessed, I'm using Linux and have only tested the extension there.
>
> You could also try the symmetric case: set repository.native = CRLF in
> the .hgeol file and test on Linux. I would say the test-eol script
> should test that as well since it tests a bunch of operations using all
> four combinations of CRLF and LF. But maybe I missed something...

It's TortoiseHg!

So I was testing to see if named branches made any difference and if -u 
vs -r mattered when I finally saw why some of my clones worked and some 
didn't.

1. All clones done via 'hg clone' properly deal with eol
2. None of the clones done using the TortoiseHg Clone gui handle eol 
correctly

This is true on Linux, too, using 'hgtk clone'.

Notably, it's just the Clone dialog that has issues.  If I use the 
Repository Explorer to 'clone to NULL; clone to tip', then it works just 
fine.

The outstanding question now is: what could TortoiseHg Clone be doing 
that makes it completely skip the hgeol extension?