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

From: Jacob Keller <jacob.keller@gmail.com>
Date: Jan 7, 2016, 23:25 UTC
Message-ID: <CA+P7+xpUW6as6aary+33V6sMo=BysFHpng6XeRRpXh2vXNKd=g@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.
>
>

Infact, even running

git fetch origin +refs/changes/98/73598/1:refs/changes/98/73598/1

does not end up placing anything into refs/changes?

Is it because it happens to not be known by git? That seems rather short sighted...

Regards, Jake