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

Re: Refspec wildcards for remotes require trailing slash

From
MGMonte Goulding <monte@sweattechnologies.com>
Date
Dec 10, 2013, 19:59 UTC
Message-ID
<569D9126-F0FB-41A2-AB83-D002C2C2B679@sweattechnologies.com>
In-Reply-To
<xmqqzjo8tt5y.fsf@gitster.dls.corp.google.com>
On 11/12/2013, at 6:14 AM, Junio C Hamano <gitster@pobox.com> 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 the list
Previous: Junio C Hamano
Message 3 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.