summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-01-08 21:23:26 (GMT)
committerJunio C Hamano <gitster@pobox.com>2013-01-08 21:23:26 (GMT)
commit69637e5e6d79dbef18ebb89c7d1885cca30496f4 (patch)
treeccccedfe607cac884c1f0269cc62fcc4e8d9abaa
parent8d1b1a02493072aeb11fa8d6d27759a917e7aad5 (diff)
parentb5fb4770ad132f1e3458dae61b132e335898dc9e (diff)
downloadgit-69637e5e6d79dbef18ebb89c7d1885cca30496f4.zip
git-69637e5e6d79dbef18ebb89c7d1885cca30496f4.tar.gz
git-69637e5e6d79dbef18ebb89c7d1885cca30496f4.tar.bz2
Merge branch 'kb/maint-bundle-doc'
* 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 16a6b0a..bc023cc 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