Re: git bundle unbundle and "check-outable" refs

From: Jakub Narebski <jnareb@gmail.com>
Date: Sep 29, 2011, 17:20 UTC
Message-ID: <m3ty7vnu4g.fsf@localhost.localdomain>
In-Reply-To: <dec8c877-bd6e-4120-b045-87179d54abe2@i30g2000yqd.googlegroups.com>

"Todd A. Jacobs" <nospam+listmail@codegnome.org> writes:

Show 8 quoted lines

> Never having needed git bundle before, I've recently been using it as
> a sneakernet. In particular, I'm using bundles to work around
> limitations of filesystem semantics on vfat and hpfs+ drives when
> shared between Linux and OS X systems. The systems are air-gapped, so
> sneakernet is essential.
> 
> At any rate, the issue I'm dealing with is that "git bundle unbundle"
> is sort of non-intuitive to deal with. [...]

I guess the fault is with "git bundle" documentation.

The "Example" section of git-bundle(1) manpage shows that you can use path to bundle in place of URL to repository in "git clone". Actually you can use path to bundle anywhere where URL or nickname of repository is/can be used, i.e.:

  git remote add <name> <bundle>
  git fetch <bundle> [<refspec>...]
  git pull <bundle>  [<refspec>...]

  git ls-remote <bundle>

HTH

-- 
Jakub Narębski