From: Junio C Hamano <gitster@pobox.com>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/7] check-ref-format --branch: give Porcelain a way to grok branch shorthand
Date: Sun, 22 Mar 2009 14:58:42 -0700 [thread overview]
Message-ID: <7v8wmxdxt9.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 36ca99e90903220318g2cfb192fi9d4ef0da95e1a65b@mail.gmail.com
Bert Wesarg <bert.wesarg@googlemail.com> writes:
>> int cmd_check_ref_format(int argc, const char **argv, const char *prefix)
>> {
>> + if (argc == 3 && !strcmp(argv[1], "--branch")) {
>> + struct strbuf sb = STRBUF_INIT;
>> + strbuf_branchname(&sb, argv[2]);
>
> strbuf_branchname() will be introduced in the next patch!
Good eyes; thanks.
next prev parent reply other threads:[~2009-03-22 22:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 22:13 [PATCH 0/7] Clean up interpret_nth_last_branch feature Junio C Hamano
2009-03-21 22:13 ` [PATCH 1/7] check_ref_format(): tighten refname rules Junio C Hamano
2009-03-21 22:13 ` [PATCH 2/7] Rename interpret/substitute nth_last_branch functions Junio C Hamano
2009-03-21 22:13 ` [PATCH 3/7] check-ref-format --branch: give Porcelain a way to grok branch shorthand Junio C Hamano
2009-03-21 22:13 ` [PATCH 4/7] strbuf_branchname(): a wrapper for branch name shorthands Junio C Hamano
2009-03-21 22:13 ` [PATCH 5/7] Fix "branch -m @{-1} newname" Junio C Hamano
2009-03-21 22:13 ` [PATCH 6/7] strbuf_check_branch_ref(): a helper to check a refname for a branch Junio C Hamano
2009-03-21 22:13 ` [PATCH 7/7] checkout -: make "-" to mean "previous branch" everywhere Junio C Hamano
2009-03-22 0:58 ` [PATCH 7/7 (v2)] " Junio C Hamano
2009-03-22 10:18 ` [PATCH 3/7] check-ref-format --branch: give Porcelain a way to grok branch shorthand Bert Wesarg
2009-03-22 21:58 ` Junio C Hamano [this message]
2009-03-21 23:15 ` [PATCH 1/7] check_ref_format(): tighten refname rules Junio C Hamano
2009-03-22 14:41 ` Johannes Schindelin
2009-03-22 23:19 ` Junio C Hamano
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=7v8wmxdxt9.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bert.wesarg@googlemail.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).