{"thread":{"id":"11202","subject":"Where has \"git ls-remote\" reference pattern matching gone?","startedAt":"2007-12-08T22:05:14Z","lastAt":"2007-12-09T15:38:03Z","messageCount":4,"participants":["Eyvind Bernhardsen","Junio C Hamano","Daniel Barkalow"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"62436","messageId":"4E5E5B1E-A303-45C9-9944-57D54FD50F80@orakel.ntnu.no","threadId":"11202","inReplyTo":null,"subject":"Where has \"git ls-remote\" reference pattern matching gone?","fromName":"Eyvind Bernhardsen","fromEmail":"eyvind-git@orakel.ntnu.no","sentAt":"2007-12-08T22:05:14Z","receivedAt":"2007-12-08T22:05:14Z","isPatch":false,"sender":{"key":"eyvind.bernhardsen@gmail.com","avatar":"https://avatars.githubusercontent.com/u/106762?v=4"},"body":"git-ls-remote(1) says that ls-remote supports filtering by reference  \nname:\n\n\n> SYNOPSIS\n>        git-ls-remote [--heads] [--tags]  [-u <exec> | --upload-pack  \n> <exec>]\n>                      <repository> <refs>...\n>\n> [...]\n>\n>        <refs>...\n>               When unspecified, all references, after filtering done  \n> with\n>               --heads and --tags, are shown. When <refs>... are  \n> specified,\n>               only references matching the given patterns are  \n> displayed.\n>\n> [...]\n>\n>        $ git ls-remote --tags public v\\*\n>        d6602ec5194c87b0fc87103ca4d67251c76f233a        refs/tags/v0.99\n>        f25a265a342aed6041ab0cc484224d9ca54b6f41        refs/tags/ \n> v0.99.1\n>        c5db5456ae3b0873fc659c19fafdde22313cc441        refs/tags/ \n> v0.99.2\n>        7ceca275d047c90c0c7d5afb13ab97efdf51bd6e        refs/tags/ \n> v0.99.3\n\nBut when I try to use the <refs> argument on a current build of git  \n(git version v1.5.3.7-1112-g9758ecd), I just get its usage message,  \nwhich doesn't mention that argument:\n\n> vredefort:[backup]% git ls-remote origin foob\n> usage: git-ls-remote [--upload-pack=<git-upload-pack>]  \n> [<host>:]<directory>\n\n\nls-remote was recently made a builtin; was reference filtering  \ndeliberately removed, or was it just lost in translation from the  \nshell script?\n\nEyvind Bernhardsen\n"},{"id":"62442","messageId":"7vve78tzw1.fsf@gitster.siamese.dyndns.org","threadId":"11202","inReplyTo":"4E5E5B1E-A303-45C9-9944-57D54FD50F80@orakel.ntnu.no","subject":"Re: Where has \"git ls-remote\" reference pattern matching gone?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-12-09T01:34:06Z","receivedAt":"2007-12-09T01:34:06Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Eyvind Bernhardsen <eyvind-git@orakel.ntnu.no> writes:\n\n> ls-remote was recently made a builtin; was reference filtering\n> deliberately removed, or was it just lost in translation from the\n> shell script?\n\nI suspect that to be the case.  Daniel, I think this is yours.\n"},{"id":"62446","messageId":"Pine.LNX.4.64.0712082048570.5349@iabervon.org","threadId":"11202","inReplyTo":"7vve78tzw1.fsf@gitster.siamese.dyndns.org","subject":"Re: Where has \"git ls-remote\" reference pattern matching gone?","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2007-12-09T02:20:50Z","receivedAt":"2007-12-09T02:20:50Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Sat, 8 Dec 2007, Junio C Hamano wrote:\n\n> Eyvind Bernhardsen <eyvind-git@orakel.ntnu.no> writes:\n> \n> > ls-remote was recently made a builtin; was reference filtering\n> > deliberately removed, or was it just lost in translation from the\n> > shell script?\n> \n> I suspect that to be the case.  Daniel, I think this is yours.\n\nAh, sure enough. I didn't see that feature there, I guess. Am I right that \nit's supposed to have \"git ls-remote origin db/*\" return refs of the \nform \"*/db/*\", interpreted as for globs?\n\nEyvind: can I get a test case? I haven't ever used this feature, and I'm \nnot sure I'll implement it correctly.\n\n\t-Daniel\n*This .sig left intentionally blank*\n"},{"id":"62488","messageId":"135A5AE4-45F9-47BC-8727-68C6680B6EEF@orakel.ntnu.no","threadId":"11202","inReplyTo":"Pine.LNX.4.64.0712082048570.5349@iabervon.org","subject":"Re: Where has \"git ls-remote\" reference pattern matching gone?","fromName":"Eyvind Bernhardsen","fromEmail":"eyvind-git@orakel.ntnu.no","sentAt":"2007-12-09T15:38:03Z","receivedAt":"2007-12-09T15:38:03Z","isPatch":false,"sender":{"key":"eyvind.bernhardsen@gmail.com","avatar":"https://avatars.githubusercontent.com/u/106762?v=4"},"body":"On 9. des.. 2007, at 03.20, Daniel Barkalow wrote:\n\n> On Sat, 8 Dec 2007, Junio C Hamano wrote:\n>\n>> Eyvind Bernhardsen <eyvind-git@orakel.ntnu.no> writes:\n>>\n>>> ls-remote was recently made a builtin; was reference filtering\n>>> deliberately removed, or was it just lost in translation from the\n>>> shell script?\n>>\n>> I suspect that to be the case.  Daniel, I think this is yours.\n>\n> Ah, sure enough. I didn't see that feature there, I guess. Am I  \n> right that\n> it's supposed to have \"git ls-remote origin db/*\" return refs of the\n> form \"*/db/*\", interpreted as for globs?\n>\n> Eyvind: can I get a test case? I haven't ever used this feature, and  \n> I'm\n> not sure I'll implement it correctly.\n\nI've noticed that a fix made it to master already; that's fast work by  \nyou and Junio!  Unfortunately, it fails the test case I was going to  \nsuggest, which is the one in the ls-remote manpage (see my response in  \nthe patch thread).\n\nI haven't used the ref matching for anything (yet), so I don't have  \nany other test cases.\n\nEyvind Bernhardsen\n"}]}