summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-01-11 16:47:56 -0800
committerJunio C Hamano <gitster@pobox.com>2013-01-11 16:47:56 -0800
commit37a11306d53c426c95d6736bdb7068c9bf19d0a1 (patch)
treee2880ed009f75b825daea7f610dadcc8ac79b7eb
parentb88cb8815879beefce4cfd83261adea728752c25 (diff)
parentb5fb4770ad132f1e3458dae61b132e335898dc9e (diff)
downloadgit-37a11306d53c426c95d6736bdb7068c9bf19d0a1.tar.gz
Merge branch 'kb/maint-bundle-doc' into maint
* kb/maint-bundle-doc: Documentation: full-ness of a bundle is significant for cloning Documentation: correct example restore from bundle
-rw-r--r--Documentation/git-bundle.txt9
1 files changed, 4 insertions, 5 deletions
diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt
index 16a6b0aceb..bc023cc5f3 100644
--- a/Documentation/git-bundle.txt
+++ b/Documentation/git-bundle.txt
@@ -112,13 +112,12 @@ 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:
+Then you transfer file.bundle to the target machine B. Because this
+bundle does not require any existing object to be extracted, you can
+create a new repository on machine B by cloning from it:
----------------
-machineB$ git clone /home/me/tmp/file.bundle R2
+machineB$ git clone -b master /home/me/tmp/file.bundle R2
----------------
This will define a remote called "origin" in the resulting repository that