On Fri, Sep 20, 2013 at 8:52 AM, Martin Gregory
wrote:
> Something that would help is an easier way to debug sparse-checkout rules.
>
> When something goes wrong, there appears to be no way to understand what
> git thinks it's reading. I'm not sure if such a way, if it existed, would
> help wit
Thanks Duy for the fast response.
> 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, bu
2 matches
Mail list logo