Jacob Keller <jacob.keller@xxxxxxxxx> writes: > On Thu, Jan 7, 2016 at 3:06 PM, Jacob Keller <jacob.keller@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html