Re: Refspec wildcards for remotes require trailing slash

On 11/12/2013, at 6:14 AM, Junio C Hamano wrote: > But it is debatable if such a change should allow "refs/a/b*" to > match "refs/a/b/2". Arguments can be made in both ways, and my > knee-jerk reaction is it shouldn't. Hmm.. for-each-ref doesn't match it but ls-remote does Sorry: forgot to CC

Refspec wildcards for remotes require trailing slash

Hi I came across this issue the other day while trying to optimise a fetch to a repo with release branches named release-X.X.X. I wanted to just fetch just those branches but because of the trailing slash rule I couldn't. The following StackOverflow post has details of the issue: http://stack