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

Re: [PATCH] Documentation: clarify / requirement in 'git check-ref-format'

From
Geoff Russell <geoffrey.russell@gmail.com>
Date
May 18, 2009, 02:36 UTC
Message-ID
<93c3eada0905171936u2e6d67d5mc7eb80936b710a6b@mail.gmail.com>
In-Reply-To
<1242229386-27486-1-git-send-email-git@drmicha.warpmail.net>

On Thu, May 14, 2009 at 1:13 AM, Michael J Gruber <git@drmicha.warpmail.net> wrote:

Show 14 quoted lines
> 'git check-ref-format' checks for the presence of at least one '/', the
> idea being that there should be no refs directly below 'refs/', so there
> should be a category like 'heads/' or 'tags/' in a refname.
>
> Try and make this clearer in the man page.
>
> [....snip]
> +. They must contain at least one `/`. This enforces the presence of a
> +  category like `heads/`, `tags/` etc. but the actual names are not
> +  restricted.
> +
>  . They cannot have two consecutive dots `..` anywhere.
>
> [ ...snip]
Ah, okay. This is clear. Many thanks.

Cheers, Geoff

Previous: Michael J GruberNext: Geoff Russell
Message 6 of 8 in “check-ref-format question”
  1. Geoff RussellMay 13, 2009
  2. Michael J GruberMay 13, 2009
  3. Sverre RabbelierMay 13, 2009
  4. Daniel BarkalowMay 13, 2009
  5. Documentation: clarify / requirement in 'git check-ref-format'Michael J Gruber, May 13, 2009
  6. Geoff RussellMay 18, 2009
  7. Geoff RussellMay 14, 2009
  8. Michael J GruberMay 14, 2009

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.