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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 4, 2012, 19:28 UTC
Message-ID
<7v391uyr2w.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAAmo=1BU5N8nbonEb1aZEx=-e8VexwsE74pjm_56dXmCDK+K6g@mail.gmail.com>
Ben Olive <sionide21@gmail.com> writes:
> My `.git/config` can be corrupted if I try to get a local branch with
> an extremely long name to track a remote branch.
>
> Here is a (contrived) example to reproduce the issue:
Don't do that, then ;-)
I think we have a change that is already cooking.

Ben (Walton), want to add a test for your 0971e99 (Remove the hard coded length limit on variable names in config files, 2012-09-30) before it hits 'next', perhaps?

Previous: Jeff KingNext: Jeff King
Message 3 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.