From: Junio C Hamano <gitster@pobox•com>
To: Jacob Keller <jacob.keller@gmail•com>
Cc: Git mailing list <git@vger•kernel.org>
Subject: Re: how to fetch entire heirarchy of refs from a remote?
Date: Thu, 07 Jan 2016 15:45:56 -0800 [thread overview]
Message-ID: <xmqqfuy92bt7.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CA+P7+xra4hjskOLg=VhLMGazTSDH=ky8H+fj2VMCw+HoY2Frrg@mail.gmail.com> (Jacob Keller's message of "Thu, 7 Jan 2016 15:36:30 -0800")
Jacob Keller <jacob.keller@gmail•com> writes:
> On Thu, Jan 7, 2016 at 3:06 PM, Jacob Keller <jacob.keller@gmail•com> wrote:
>>
>> But, git clone --mirror and git fetch have failed to pull every ref,
>> and only end up with heads and tags.
>>
>> Regards,
>> Jake
>
> It turns out that it *does* pull the refs, but they don't appear to
> show up inside the "refs" folder.. is there a reason for this?
>
> ie:
>
> ls .git/refs/changes
>
> shows nothing,but
>
> git ls-remote file:///path/to/repo
>
> does show them? Any particular reason for why this is? I am confused
> why refs aren't showing up inside the refs folder...
Does
git for-each-ref refs/changes/
in your local resulting repository show them?
There is nothing that says "ls -R .git/refs/" is the way to
enumerate available refs (in fact it is a _wrong_ way that is
guaranteed to give you wrong results).
Hint: .git/packed-refs
next prev parent reply other threads:[~2016-01-07 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 23:06 how to fetch entire heirarchy of refs from a remote? Jacob Keller
2016-01-07 23:15 ` Junio C Hamano
2016-01-07 23:23 ` Jacob Keller
2016-01-07 23:25 ` Jacob Keller
2016-01-07 23:36 ` Jacob Keller
2016-01-07 23:45 ` Junio C Hamano [this message]
2016-01-08 16:30 ` Jacob Keller
2016-01-07 23:39 ` Jacob Keller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqfuy92bt7.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jacob.keller@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox