From: Geoff Russell <geoffrey.russell@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Daniel Barkalow <barkalow@iabervon.org>,
Sverre Rabbelier <srabbelier@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Documentation: clarify / requirement in 'git check-ref-format'
Date: Mon, 18 May 2009 12:06:34 +0930 [thread overview]
Message-ID: <93c3eada0905171936u2e6d67d5mc7eb80936b710a6b@mail.gmail.com> (raw)
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:
> '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
next prev parent reply other threads:[~2009-05-18 2:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 0:09 check-ref-format question Geoff Russell
2009-05-13 14:13 ` Michael J Gruber
2009-05-13 14:40 ` Sverre Rabbelier
2009-05-13 15:03 ` Daniel Barkalow
2009-05-13 15:43 ` [PATCH] Documentation: clarify / requirement in 'git check-ref-format' Michael J Gruber
2009-05-18 2:36 ` Geoff Russell [this message]
2009-05-14 0:26 ` check-ref-format question Geoff Russell
2009-05-14 7:24 ` Michael J Gruber
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93c3eada0905171936u2e6d67d5mc7eb80936b710a6b@mail.gmail.com \
--to=geoffrey.russell@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@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.
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 NNTP newsgroup(s).