From: Geoff Russell <geoffrey.russell@gmail.com>
To: git@vger.kernel.org
Subject: check-ref-format question
Date: Wed, 13 May 2009 09:39:28 +0930 [thread overview]
Message-ID: <93c3eada0905121709k73a47bddu60def6b5fbc1b15e@mail.gmail.com> (raw)
1 $ git --version
git version 1.6.2.3
2 $ git check-ref-format xxxx && echo OK
3 $ git-check-ref-format --branch xxxx && echo OK
xxxx
OK
4 $ git check-ref-format --branch xxxx && echo OK
usage: git check-ref-format refname
2 seems wrong,
I tried 3 after looking at builtin-check-ref-format.c
I couldn't find any test cases in the git/t directory
>From the documenation, I expect "git check-ref-format xxx" to return 0 if xxx is
a valid branch or ref name. git version 1.6.3 gives the same results.
Cheers,
Geoff.
next reply other threads:[~2009-05-13 0:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 0:09 Geoff Russell [this message]
2009-05-13 14:13 ` check-ref-format question 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
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=93c3eada0905121709k73a47bddu60def6b5fbc1b15e@mail.gmail.com \
--to=geoffrey.russell@gmail.com \
--cc=git@vger.kernel.org \
/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).