From: Andrew Ardill <andrew.ardill@gmail.com>
Date: Fri, 05 Oct 2012 00:36:52 GMT
Subject: Re: Super long branch names corrupt `.git/config`
Message-ID: <CAH5451=fEDd+EvgEst_G00nQ-yot+2UCbWt_UpduR57bhxHYew@mail.gmail.com>
In-Reply-To: <20121005002942.GB17586@sigill.intra.peff.net>

On 5 October 2012 10:29, Jeff King <peff@peff.net> wrote:
>...
>
>but it feels a little fake. Why 200? Because that will test the config
>limit, but will not overflow the NAME_MAX limit (at least not on
>Linux! No clue on other platforms) when we try to create
>refs/heads/foo-$z200.

I can't test this particular case right now, but I recently had an
issue with Windows Server 2008 due to a long filename, that
essentially meant I couldn't move, change owner or change permissions
on the given file. Unless someone has more info I can test a bit
later. Is the idea that we shouldn't allow filenames that will cause
issues with the underlying OS (or other people's OS) or something
else?

Regards,

Andrew Ardill