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

Re: how to fetch entire heirarchy of refs from a remote?

From
Jacob Keller <jacob.keller@gmail.com>
Date
Jan 7, 2016, 23:23 UTC
Message-ID
<CA+P7+xrZKqchLUwp7tPaydsm5cdcHx38oU9=kPjen-A2Pvkx0g@mail.gmail.com>
In-Reply-To
<xmqqpoxd2d74.fsf@gitster.mtv.corp.google.com>
On Thu, Jan 7, 2016 at 3:15 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 24 quoted lines
> Jacob Keller <jacob.keller@gmail.com> writes:
>
>> refs/changes/98/47298/3
>> refs/changes/98/57298/1
>> refs/changes/98/57298/2
>> refs/changes/98/73598/1
>> refs/changes/99/44099/1
>> refs/changes/99/69299/1
>>
>>
>> Is it possible to specify a refspec such that all of these will be
>> fetched? I tried doing
>>
>> +refs/changes/*:refs/changes/*
>>
>> but this doesn't work since the * can only be one portion of a refspec
>
> I am not sure if I follow.  With refs/heads/*:refs/remotes/origin/*
> (e.g. following git://github.com/gitster/git for example), I am
> reasonably sure you would get my refs/heads/jk/notes-dwim-doc and
> other topics you authored without the slash between jk and
> notes-dwim-doc getting in the way.
>
>
That appears to be correct, but.. why doesn't:
git fetch origin +refs/changes/*:refs/changes/*
seem to anything at all?

Ideally this owuld fetch all the remote refs in refs/changes and stick them into my refs, but it appears to do nothing at all.

Regards, Jake

Previous: Junio C HamanoNext: Jacob Keller
Message 3 of 8 in “how to fetch entire heirarchy of refs from a remote?”
  1. Jacob KellerJan 7, 2016
  2. Junio C HamanoJan 7, 2016
  3. Jacob KellerJan 7, 2016
  4. Jacob KellerJan 7, 2016
  5. Jacob KellerJan 7, 2016
  6. Junio C HamanoJan 7, 2016
  7. Jacob KellerJan 8, 2016
  8. Jacob KellerJan 7, 2016

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.