| commit | f22a6543d17d615068652d0f94397f558158d91a | |
| author | W. Trevor King <wking@tremily.us> | |
| Sat, 22 Jun 2013 14:46:25 +0000 (22 10:46 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 23 Jun 2013 06:35:00 +0000 (22 23:35 -0700) | ||
| tree | 424a20c22a9eddc2564167459be61cd7eff29f9c | treesnapshot (tar.gz zip) |
| parent | 8c8fc53c7d3daf07f690c1d88ce45849663e6fa4 | commitdiff |
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>
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>
| Documentation/git-clone.txt | diffblobblamehistory |