From: Junio C Hamano <gitster@pobox.com>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [RFC/PATCH 3/2] rev-parse: --abbrev-ref option to shorten ref name
Date: Mon, 13 Apr 2009 09:43:42 -0700 [thread overview]
Message-ID: <7vhc0sh5c1.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1239621626-26952-1-git-send-email-bert.wesarg@googlemail.com> (Bert Wesarg's message of "Mon, 13 Apr 2009 13:20:26 +0200")
Bert Wesarg <bert.wesarg@googlemail.com> writes:
> This applies the shorten_unambiguous_ref function to the object name.
> Default mode is controlled by core.warnAmbiguousRefs. Else it is given as
> optional argument to --abbrev-ref={strict|loose}.
>
> This should be faster than 'git for-each-ref --format="%(refname:short)" <ref>'
> for single refs.
>
> Signed-off-by: Bert Wesarg <bert.wesarg@googlemail.com>
> ---
> Cc: Jeff King <peff@peff.net>
> Cc: git@vger.kernel.org
>
> Can someone check, if I need to alter the filter, thanks.
I do not think so.
This --abbrev-ref option is similar to --symbolic in that how a ref from
the command line, if any, is output, and should not change the filter at
all. For example, "rev-parse --abbrev-ref master -M" shouldn't filter -M
out by implying --revs-only.
prev parent reply other threads:[~2009-04-13 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 10:25 [PATCH 1/2] shorten_unambiguous_ref(): add strict mode Bert Wesarg
2009-04-13 10:25 ` [PATCH 2/2] for-each-ref: utilize core.warnAmbiguousRefs for :short-format Bert Wesarg
2009-04-13 11:20 ` [RFC/PATCH 3/2] rev-parse: --abbrev-ref option to shorten ref name Bert Wesarg
2009-04-13 16:43 ` Junio C Hamano [this message]
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=7vhc0sh5c1.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).