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>

W. Trevor King committed Jun 22, 2013 at 10:46 UTC f22a6543d17d615068652d0f94397f558158d91a
1 file changed +4 -4
Documentation/git-clone.txt
+4 -4
@@ -257,10 +257,10 @@ $ git show-branch
257 * Clone from upstream while borrowing from an existing local directory:
258 +
259 ------------
260 -$ git clone --reference my2.6 \
261 - git://git.kernel.org/pub/scm/.../linux-2.7 \
262 - my2.7
263 -$ cd my2.7
260 +$ git clone --reference /git/linux.git \
261 + git://git.kernel.org/pub/scm/.../linux.git \
262 + my-linux
263 +$ cd my-linux
264 ------------
265
266