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

Re: [PATCH] gitremote-helpers(1): clarify refspec behaviour

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Apr 17, 2013, 22:30 UTC
Message-ID
<CAMP44s38Cqcr4mwDBexW4tHzv3BKffCYEn5oN0U6Wji10nmJMw@mail.gmail.com>
In-Reply-To
<505914600ac7f4afc26f8b29fbece26156c87519.1365272021.git.john@keeping.me.uk>
On Sat, Apr 6, 2013 at 12:13 PM, John Keeping <john@keeping.me.uk> wrote:
Show 10 quoted lines
> --- a/Documentation/gitremote-helpers.txt
> +++ b/Documentation/gitremote-helpers.txt
> @@ -174,8 +174,8 @@ ref.
>  This capability can be advertised multiple times.  The first
>  applicable refspec takes precedence.  The left-hand of refspecs
>  advertised with this capability must cover all refs reported by
> -the list command.  If no 'refspec' capability is advertised,
> -there is an implied `refspec *:*`.
> +the list command.  If a helper does not need a specific 'refspec'
> +capability then it should advertise `refspec *:*`.

But if it advertises a straight 'refspec *:*', nothing would work. If anything, it should be 'refs/heads/*:refs/remotes/$alias/*', but then tags would fail. Why not just tell the remote helpers to do the right thing and avoid this comment altogether?

-- 
Felipe Contreras
Previous: Sverre Rabbelier
Message 3 of 3 in “gitremote-helpers(1): clarify refspec behaviour”
  1. gitremote-helpers(1): clarify refspec behaviourJohn Keeping, Apr 6, 2013
  2. Sverre RabbelierApr 6, 2013
  3. Felipe ContrerasApr 17, 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.