From: Duy Nguyen <pclouds@gmail.com>
Date: Fri, 20 Sep 2013 01:15:28 GMT
Subject: Re: re[4]: sparse checkout file with windows line endings doesn't work
Message-ID: <CACsJy8BeT7ZP+ZQah7FR6ogqRNiiDZYP5SEs8J6J=+gEHU5MUg@mail.gmail.com>
In-Reply-To: <SDZYRFhOTCk2PDAuPVQvMjI4MjE1ODkw@IBMLT4>

On Fri, Sep 20, 2013 at 7:01 AM, Martin Gregory
<marting@adelaideinterim.com.au> wrote:
> Hi Duy ,
>
> re: [file created in gitbash]
>
>>>  Thanks. Please send me the file created by windows shell. I suspected
>>>  that windows shell may save it in some funny encoding like utf-16..
>
>
> Strangely, I had sent the file created by the windows shell ahead of the one
> created by gitbash, but here it is again :)

Sorry I must have missed it. Anyway there is a trailing space at the
end of the rule. This is the content of your sparse checkout file in C
syntax

"/CONFIGURATION\x20\r\n"

Maybe we could warn about trailing spaces.. Stripping them
automatically is a possibility, but we need an escape hatch for
(crazy?) people who actually have trailing spaces in there paths.
-- 
Duy