table of contents
other versions
- jessie 1:2.1.4-2.1+deb8u6
- jessie-backports 1:2.11.0-3~bpo8+1
- stretch 1:2.11.0-3+deb9u4
- testing 1:2.20.1-2
- stretch-backports 1:2.20.1-1~bpo9+1
- unstable 1:2.20.1-2
- experimental 1:2.21.0+next.20190320-1
GIT-BUNDLE(1) | Git Manual | GIT-BUNDLE(1) |
NAME¶
git-bundle - Move objects and refs by archiveSYNOPSIS¶
git bundle create <file> <git-rev-list-args> git bundle verify <file> git bundle list-heads <file> [<refname>...] git bundle unbundle <file> [<refname>...]
DESCRIPTION¶
Some workflows require that one or more branches of development on one machine be replicated on another machine, but the two machines cannot be directly connected, and therefore the interactive Git protocols (git, ssh, http) cannot be used. This command provides support for git fetch and git pull to operate by packaging objects and references in an archive at the originating machine, then importing those into another repository using git fetch and git pull after moving the archive by some means (e.g., by sneakernet). As no direct connection between the repositories exists, the user must specify a basis for the bundle that is held by the destination repository: the bundle assumes that all objects in the basis are already in the destination repository.OPTIONS¶
create <file>Used to create a bundle named file. This requires
the git-rev-list-args arguments to define the bundle contents.
verify <file>
Used to check that a bundle file is valid and will apply
cleanly to the current repository. This includes checks on the bundle format
itself as well as checking that the prerequisite commits exist and are fully
linked in the current repository. git bundle prints a list of missing
commits, if any, and exits with a non-zero status.
list-heads <file>
Lists the references defined in the bundle. If followed
by a list of references, only references matching those given are printed
out.
unbundle <file>
Passes the objects in the bundle to git index-pack
for storage in the repository, then prints the names of all defined
references. If a list of references is given, only references matching those
in the list are printed. This command is really plumbing, intended to be
called only by git fetch.
<git-rev-list-args>
A list of arguments, acceptable to git rev-parse
and git rev-list (and containing a named ref, see SPECIFYING REFERENCES
below), that specifies the specific objects and references to transport. For
example, master~10..master causes the current master reference to be
packaged along with all objects added since its 10th ancestor commit. There is
no explicit limit to the number of references and objects that may be
packaged.
[<refname>...]
A list of references used to limit the references
reported as available. This is principally of use to git fetch, which
expects to receive only those references asked for and not necessarily
everything in the pack (in this case, git bundle acts like git
fetch-pack).
SPECIFYING REFERENCES¶
git bundle will only package references that are shown by git show-ref: this includes heads, tags, and remote heads. References such as master~1 cannot be packaged, but are perfectly suitable for defining the basis. More than one reference may be packaged, and more than one basis can be specified. The objects packaged are those not contained in the union of the given bases. Each basis can be specified explicitly (e.g. ^master~10), or implicitly (e.g. master~10..master, --since=10.days.ago master). It is very important that the basis used be held by the destination. It is okay to err on the side of caution, causing the bundle file to contain objects already in the destination, as these are ignored when unpacking at the destination.EXAMPLE¶
Assume you want to transfer the history from a repository R1 on machine A to another repository R2 on machine B. For whatever reason, direct connection between A and B is not allowed, but we can move data from A to B via some mechanism (CD, email, etc.). We want to update R2 with development made on the branch master in R1. To bootstrap the process, you can first create a bundle that does not have any basis. You can use a tag to remember up to what commit you last processed, in order to make it easy to later update the other repository with an incremental bundle:machineA$ cd R1 machineA$ git bundle create file.bundle master machineA$ git tag -f lastR2bundle master
machineB$ git clone -b master /home/me/tmp/file.bundle R2
[remote "origin"] url = /home/me/tmp/file.bundle fetch = refs/heads/*:refs/remotes/origin/*
machineA$ cd R1 machineA$ git bundle create file.bundle lastR2bundle..master machineA$ git tag -f lastR2bundle master
machineB$ cd R2 machineB$ git pull
$ git bundle create mybundle v1.0.0..master
$ git bundle create mybundle --since=10.days master
$ git bundle create mybundle -10 master
$ git bundle verify mybundle
$ git fetch mybundle master:localRef
$ git ls-remote mybundle
GIT¶
Part of the git(1) suite05/15/2017 | Git 2.11.0 |