summaryrefslogtreecommitdiff
path: root/Documentation/git-clone.txt
diff options
context:
space:
mode:
authorW. Trevor King <wking@tremily.us>2013-06-22 10:46:25 -0400
committerJunio C Hamano <gitster@pobox.com>2013-06-22 23:35:00 -0700
commitf22a6543d17d615068652d0f94397f558158d91a (patch)
tree424a20c22a9eddc2564167459be61cd7eff29f9c /Documentation/git-clone.txt
parent8c8fc53c7d3daf07f690c1d88ce45849663e6fa4 (diff)
downloadgit-f22a6543d17d615068652d0f94397f558158d91a.tar.gz
doc/clone: Pick more compelling paths for the --reference example
There may be times when using one of your local repositories as a reference for a new clone make sense, but the implied version-bump in the old example isn't one of them. I think a more intuitive example is multi-user system with a central reference clone, and the new paths hint at this use case. Signed-off-by: W. Trevor King <wking@tremily.us> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-clone.txt')
-rw-r--r--Documentation/git-clone.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index d8a64d4a99..84729b0887 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -257,10 +257,10 @@ $ git show-branch
* Clone from upstream while borrowing from an existing local directory:
+
------------
-$ git clone --reference my2.6 \
- git://git.kernel.org/pub/scm/.../linux-2.7 \
- my2.7
-$ cd my2.7
+$ git clone --reference /git/linux.git \
+ git://git.kernel.org/pub/scm/.../linux.git \
+ my-linux
+$ cd my-linux
------------