git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Refspec wildcards for remotes require trailing slash

From
MGMonte Goulding <monte@sweattechnologies.com>
Date
Dec 10, 2013, 02:32 UTC
Message-ID
<3B290FD1-EF2B-4419-8845-45C5A3B4A3D3@sweattechnologies.com>
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://stackoverflow.com/questions/20450003/is-it-possible-to-use-filters-in-refspec-in-places-other-than-directory-namespac
The trailing slash rule appears to be introduced in 46220ca and further tightened in b2a5627
Before I go ahead and look at what needs to be done for a patch I thought it would be polite to ask if there is any reasoning behind the trailing slash rule that I'm missing? Or if you are interested in changing this behavior at all.
Cheers
Monte
Next: Junio C Hamano
Message 1 of 3 in “Refspec wildcards for remotes require trailing slash”
  1. Monte GouldingDec 10, 2013
  2. Junio C HamanoDec 10, 2013
  3. Monte GouldingDec 10, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.