Re: [PATCH] for-each-ref: `:short` format for `refname`

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Bert Wesarg" <bert.wesarg@xxxxxxxxxxxxxx> writes:

> On Mon, Sep 1, 2008 at 21:10, Shawn O. Pearce <spearce@xxxxxxxxxxx> wrote:
> ...
>> You can still get ambiguous names.  Avoiding them requires going
>> through all refs and building their short forms, then using the
>> full ref name for any ref which had more than one name shorten to
>> the same string.  Ugly, but implementable, and probably something
>> that should be considered.
>
> What about: try the list backwards until the first match, than try the
> matched part (this what %.*s matched) with the forward list, if both
> give the same pattern, its not disambiguous. If not try the next
> pattern backwards.

How does it catch the case where you have both 'xyzzy' branch and 'xyzzy'
tag, which is the point of disambiguation issue Shawn raised?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux