From: Junio C Hamano <gitster@pobox.com>
To: Ben Olive <sionide21@gmail.com>
Cc: git@vger.kernel.org, Ben Walton <bdwalton@gmail.com>
Subject: Re: Super long branch names corrupt `.git/config`
Date: Thu, 04 Oct 2012 12:28:39 -0700 [thread overview]
Message-ID: <7v391uyr2w.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAAmo=1BU5N8nbonEb1aZEx=-e8VexwsE74pjm_56dXmCDK+K6g@mail.gmail.com> (Ben Olive's message of "Thu, 4 Oct 2012 13:15:25 -0400")
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?
next prev parent reply other threads:[~2012-10-04 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 17:15 Super long branch names corrupt `.git/config` Ben Olive
2012-10-04 18:29 ` Jeff King
2012-10-04 19:28 ` Junio C Hamano [this message]
2012-10-05 0:29 ` Jeff King
2012-10-05 0:36 ` Andrew Ardill
2012-10-05 15:38 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v391uyr2w.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bdwalton@gmail.com \
--cc=git@vger.kernel.org \
--cc=sionide21@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).