From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] remote.c: use shorten_unambiguous_ref
Date: Tue, 14 Apr 2009 14:55:14 +0200 [thread overview]
Message-ID: <49E487B2.5030606@drmicha.warpmail.net> (raw)
In-Reply-To: <20090410171458.GA26478@sigill.intra.peff.net>
Jeff King venit, vidit, dixit 10.04.2009 19:14:
> On Thu, Apr 09, 2009 at 05:33:02PM +0200, Michael J Gruber wrote:
>
>> Use the new shorten_unambiguous_ref() for simplifying the output of
>> upstream branch names. This affects status and checkout.
>
> Yeah, this is the spot I was thinking about when I mentioned "use it in
> other places" earlier in the thread. So
>
> Acked-by: Jeff King <peff@peff.net>
>
>> I haven't seen more obvious place for using shorten_unambiguous_ref().
>> prettify_ref() is a natural candidate but is mostly used for
>> prettyfying refs on the remote side. git branch is covered by Jeff's
>> patch already.
>
> Hmm. I was thinking we might be able to just do away with prettify_ref,
> but I didn't consider the fact that we need to prettify remote things. I
> think you could still unambiguously prettify the local half of those
> callsites, though.
>
> Given that the two functions are closely related, should we perhaps
> rename them to
>
> const char *shorten_ref(const char *);
> const char *shorten_ref_unambiguous(const char *);
>
> ? The implementations are quite different, with prettify_ref not really
> respecting the ref lookup rules, but rather just considering a few
> pre-determined bits of the hierarchy as uninteresting. It shouldn't be
> that hard to have them both use the same implementation, like:
>
> const char *shorten_ref(const char *, int unambiguous);
>
> -Peff
Should I rebase this on top of Bert's newer patch (which has the
signature you suggest)? Currently I don't see any of them in.
Michael
next prev parent reply other threads:[~2009-04-14 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 15:33 [PATCH] remote.c: use shorten_unambiguous_ref Michael J Gruber
2009-04-10 17:14 ` Jeff King
2009-04-14 12:55 ` Michael J Gruber [this message]
2009-04-15 8:03 ` Jeff King
2009-04-14 16:55 ` Junio C Hamano
2009-04-14 18:18 ` Bert Wesarg
2009-04-15 8:12 ` Jeff King
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=49E487B2.5030606@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.