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

Re: [PATCH v2 0/7] Improved infrastructure for refname normalization

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 12, 2011, 16:44 UTC
Message-ID
<7vwrdd90df.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4E6E2122.8000201@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
> OTOH I am again having serious doubts that trying to support
> unnormalized refnames is a good idea.

Sorry, I am confused. I thought the way you are planning forward is to leave unnormalized ones unchecked as the current code does (and mark the places that do so with _unsafe()), with the eventual goal of fixing the caller to pass only normalized ones to make call to the "safe" version?

Previous: Michael HaggertyNext: Michael Haggerty
Message 11 of 13 in “Improved infrastructure for refname normalization”
  1. 0/7 Improved infrastructure for refname normalizationMichael Haggerty, Sep 10, 2011
  2. 1/7 t1402: add some more testsMichael Haggerty, Sep 10, 2011
  3. 2/7 Change bad_ref_char() to return a boolean valueMichael Haggerty, Sep 10, 2011
  4. 3/7 git check-ref-format: add options --allow-onelevel and --refspec-patternMichael Haggerty, Sep 10, 2011
  5. 4/7 Change check_ref_format() to take a flags argumentMichael Haggerty, Sep 10, 2011
  6. 5/7 Add a library function normalize_refname()Michael Haggerty, Sep 10, 2011
  7. 6/7 Do not allow ".lock" at the end of any refname componentMichael Haggerty, Sep 10, 2011
  8. 7/7 Add tools to avoid the use of unnormalized refnames.Michael Haggerty, Sep 10, 2011
  9. Junio C HamanoSep 12, 2011
  10. Michael HaggertySep 12, 2011
  11. Junio C HamanoSep 12, 2011
  12. Michael HaggertySep 13, 2011
  13. Junio C HamanoSep 13, 2011

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.