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

Re: ref-format checking regression

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Apr 27, 2012, 12:57 UTC
Message-ID
<CACBZZX6i9C-RyB9-jtJkHjYOpqgDmDcBFwe10RP+bu5PGTmP9Q@mail.gmail.com>
In-Reply-To
<20120427115000.GA8126@sigill.intra.peff.net>
On Fri, Apr 27, 2012 at 13:50, Jeff King <peff@peff.net> wrote:
Show 5 quoted lines
> 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.
> So maybe we decided not to worry about it. But I thought I'd mention it
> as a data point.

Wasn't that the one about the tightening of the ref checks breaking git clone --mirror?

In any case we should be strict on input and loose when going over existing data. It seems to me that we're using one function now to check the validity of refs when we should be using two, one for new refs, and one for reading existing data.

Previous: Jeff KingNext: Junio C Hamano
Message 2 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.