summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2013-01-01 12:46:15 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-01-01 15:48:20 -0800
commitb5fb4770ad132f1e3458dae61b132e335898dc9e (patch)
treefa88f90ba4fcb15a130e2eb4f5fa496d1d09fb80 /Documentation
parentDocumentation: correct example restore from bundle (diff)
downloadtgif-b5fb4770ad132f1e3458dae61b132e335898dc9e.tar.xz
Documentation: full-ness of a bundle is significant for cloning
Not necessarily every bundle file can be cloned from. Only the ones that do not need prerequisites can. When 1d52b02 (Documentation: minor grammatical fixes and rewording in git-bundle.txt, 2009-03-22) reworded this paragraph, it lost a critical hint to tell readers why this particular bundle can be cloned from. Resurrect it. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-bundle.txt7
1 files changed, 3 insertions, 4 deletions
diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt
index 5c8ba44c18..bc023cc5f3 100644
--- a/Documentation/git-bundle.txt
+++ b/Documentation/git-bundle.txt
@@ -112,10 +112,9 @@ 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 -b master /home/me/tmp/file.bundle R2