From f22a6543d17d615068652d0f94397f558158d91a Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Sat, 22 Jun 2013 10:46:25 -0400 Subject: [PATCH] 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 Signed-off-by: Junio C Hamano --- Documentation/git-clone.txt | 8 ++++---- 1 file 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 ------------ -- 2.11.4.GIT