SYNOPSISgit
bundle create <file>
<git-rev-list-args> git bundle verify
<file> git
bundle list-heads <file>
[<refname>…] git bundle unbundle
<file>
[<refname>…]
DESCRIPTIONSome 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, rsync, http) cannot be used. This command provides
support for OPTIONS
SPECIFYING REFERENCESgit bundle 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. EXAMPLEAssume 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 Then you transfer file.bundle to the target machine B. If you are creating the repository on machine B, then you can clone from the bundle as if it were a remote repository instead of creating an empty repository and then pulling or fetching objects from the bundle: machineB$ git clone /home/me/tmp/file.bundle R2 This will define a remote called "origin" in the resulting repository that lets you fetch and pull from the bundle. The $GIT_DIR/config file in R2 will have an entry like this: [remote "origin"] url = /home/me/tmp/file.bundle fetch = refs/heads/*:refs/remotes/origin/* To update the resulting mine.git repository, you can fetch or pull after replacing the bundle stored at /home/me/tmp/file.bundle with incremental updates. After working some more in the original repository, you can create an incremental bundle to update the other repository: machineA$ cd R1 machineA$ git bundle create file.bundle lastR2bundle..master machineA$ git tag -f lastR2bundle master You then transfer the bundle to the other machine to replace /home/me/tmp/file.bundle, and pull from it. machineB$ cd R2 machineB$ git pull If you know up
to what commit the intended recipient repository should have the
necessary objects, you can use that knowledge to specify the basis,
giving a cut-off point to limit the revisions and objects that go
in the resulting bundle. The previous example used the lastR2bundle
tag for this purpose, but you can use any other options that you
would give to the You can use a tag that is present in both: $ git bundle create mybundle v1.0.0..master You can use a basis based on time: $ git bundle create mybundle --since=10.days master You can use the number of commits: $ git bundle create mybundle -10 master You can
run $ git bundle verify mybundle This will list what commits you must have in order to extract from the bundle and will error out if you do not have them. A bundle from a recipient repository’s point of view is just like a regular repository which it fetches or pulls from. You can, for example, map references when fetching: $ git fetch mybundle master:localRef You can also see what references it offers: $ git ls-remote mybundle |
|