[PATCH v2 2/4] doc/clone: Pick more compelling paths for the --reference example
- From
W. Trevor King <wking@tremily.us>
- Date
- Jun 22, 2013, 14:46 UTC
- Message-ID
- <79c2444a4fc73cbf699f571351780ce59f5d8785.1371911897.git.wking@tremily.us>
- In-Reply-To
- <cover.1371911897.git.wking@tremily.us>
From: "W. Trevor King" <wking@tremily.us>
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> --- 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 cec6fc1..bf05ada 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 ------------
-- 1.8.3