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

Re: ref-format checking regression

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 27, 2012, 15:25 UTC
Message-ID
<xmqqipgl9oz3.fsf@junio.mtv.corp.google.com>
In-Reply-To
<xmqqr4v99pu5.fsf@junio.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 15 quoted lines
> Jeff King <peff@peff.net> writes:
>
>> I upgraded git on a machine recently, and it created problems for a repo
>> with a bogus character in a ref name.  Older versions of git never
>> complained about it. Newer ones, containing your dce4bab ("add_ref():
>> verify that the refname is formatted correctly") do. That's fine; it's
>> bogus and git _should_ complain about it.
>> 
>> However, recovering from the situation is unnecessarily hard, ...
>> ...
>> I seem to recall discussing this format-tightening and trying to be sure
>> that users were left with a way forward for fixing their repos. But I
>> can't find the discussion, and I don't recall any conclusion we came to.
>
> I haven't dug the archive but I do recall ...
A few...
  http://thread.gmane.org/gmane.comp.version-control.git/185564
  http://thread.gmane.org/gmane.comp.version-control.git/184382/focus=185483
Previous: Junio C HamanoNext: Jeff King
Message 4 of 5 in “ref-format checking regression”
  1. Jeff KingApr 27, 2012
  2. Ævar Arnfjörð BjarmasonApr 27, 2012
  3. Junio C HamanoApr 27, 2012
  4. Junio C HamanoApr 27, 2012
  5. Jeff KingApr 28, 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.