git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Super long branch names corrupt `.git/config`

From
Andrew Ardill <andrew.ardill@gmail.com>
Date
Oct 5, 2012, 00:36 UTC
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:
Show 6 quoted lines
>...
>
>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
Previous: Jeff KingNext: Jeff King
Message 5 of 6 in “Super long branch names corrupt `.git/config`”
  1. Ben OliveOct 4, 2012
  2. Jeff KingOct 4, 2012
  3. Junio C HamanoOct 4, 2012
  4. Jeff KingOct 5, 2012
  5. Andrew ArdillOct 5, 2012
  6. Jeff KingOct 5, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.