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

Previous thread: [Misfeature] cloning without configuration fails and returns 0 by Benoit Sigoure on Saturday, December 8, 2007 - 3:21 pm. (3 messages)

Next thread: What does this error mean? by Bo Yang on Saturday, December 8, 2007 - 7:24 pm. (1 message)
From: Eyvind Bernhardsen
Date: Saturday, December 8, 2007 - 3:05 pm

git-ls-remote(1) says that ls-remote supports filtering by reference  

But when I try to use the <refs> argument on a current build of git  
(git version v1.5.3.7-1112-g9758ecd), I just get its usage message,  


ls-remote was recently made a builtin; was reference filtering  
deliberately removed, or was it just lost in translation from the  
shell script?

Eyvind Bernhardsen

-

From: Junio C Hamano
Date: Saturday, December 8, 2007 - 6:34 pm

I suspect that to be the case.  Daniel, I think this is yours.
-

From: Daniel Barkalow
Date: Saturday, December 8, 2007 - 7:20 pm

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.

	-Daniel
*This .sig left intentionally blank*
-

From: Eyvind Bernhardsen
Date: Sunday, December 9, 2007 - 8:38 am

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

-

Previous thread: [Misfeature] cloning without configuration fails and returns 0 by Benoit Sigoure on Saturday, December 8, 2007 - 3:21 pm. (3 messages)

Next thread: What does this error mean? by Bo Yang on Saturday, December 8, 2007 - 7:24 pm. (1 message)