Re: Where has "git ls-remote" reference pattern matching gone?

From: Eyvind Bernhardsen <eyvind-git@orakel.ntnu.no>
Date: Dec 9, 2007, 15:38 UTC
Message-ID: <135A5AE4-45F9-47BC-8727-68C6680B6EEF@orakel.ntnu.no>
In-Reply-To: <Pine.LNX.4.64.0712082048570.5349@iabervon.org>

On 9. des.. 2007, at 03.20, Daniel Barkalow wrote:

Show 18 quoted lines

> On Sat, 8 Dec 2007, Junio C Hamano wrote:
>
>> Eyvind Bernhardsen <eyvind-git@orakel.ntnu.no> writes:
>>
>>> ls-remote was recently made a builtin; was reference filtering
>>> deliberately removed, or was it just lost in translation from the
>>> shell script?
>>
>> I suspect that to be the case.  Daniel, I think this is yours.
>
> Ah, sure enough. I didn't see that feature there, I guess. Am I  
> right that
> it's supposed to have "git ls-remote origin db/*" return refs of the
> form "*/db/*", interpreted as for globs?
>
> Eyvind: can I get a test case? I haven't ever used this feature, and  
> I'm
> not sure I'll implement it correctly.

I've noticed that a fix made it to master already; that's fast work by you and Junio! Unfortunately, it fails the test case I was going to suggest, which is the one in the ls-remote manpage (see my response in the patch thread).

I haven't used the ref matching for anything (yet), so I don't have any other test cases.

Eyvind Bernhardsen