On Tue, 17 Jan 2017 05:56:46 -0800 (PST) Ralf Tobel <ralf.to...@gmail.com> wrote:
> You're suggestion works perfectly fine. No question. > > For my case I now bundle the original repository which works also > fine and solves my problem too. > > I just wondered how I could get access to these refs which are shown > in list-heads. Well, I think you then need to define what precisely do you mean by "access". A Git bundle, IIUC, was created as a tool to facilitate data transfers from Git repos "connected over a sneakernet" (as americans call it) -- that is, not connected via a computed network, so someone needs to pass data in and out using some storage device carried around. So there are sort-of two "angles" to look at a Git bundle: * You can "unbundle" it into a local Git repository -- sort of adding what's in the bundle to what is already there. * You can fetch from a bundle -- as you would fetch from another (remote) repository. The ability to clone from a bundle is a byproduct to an ability to fetch from it because `git clone` is essentially `git init` followed by `git fetch`. Unbundling a Git bundle and fetching from it is definitely accessing the refs stored in it, so what other means of accessing them do you think of? Running `git log` on them? Diffing? `git grep`-ping? Then I think no, you can't do that. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
