summaryrefslogtreecommitdiff
path: root/Documentation/git-filter-branch.txt
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2009-08-17 06:19:17 (GMT)
committerJunio C Hamano <gitster@pobox.com>2009-08-17 07:03:39 (GMT)
commit13354f5377d82baee4d8c930df824c8dbeda396d (patch)
treecee9654d019417f210d86ab429ed5a36bfcd8b95 /Documentation/git-filter-branch.txt
parent2cd9c2aff0d65bbce704a68d9cbe7a17e02257fe (diff)
downloadgit-13354f5377d82baee4d8c930df824c8dbeda396d.zip
git-13354f5377d82baee4d8c930df824c8dbeda396d.tar.gz
git-13354f5377d82baee4d8c930df824c8dbeda396d.tar.bz2
docs: describe impact of repack on "clone -s"
The effects of repacking on a repository with alternates are a bit subtle. The two main things users will want are: 1. Not to waste disk space by accidentally copying objects which could be shared. 2. Copying all objects explicitly to break the dependency on the source repo. This patch describes both under the "clone -s" documentation. It makes sense to put it there rather than in git-repack.txt for both cases. For (1), we are warning the user who is using "clone -s" about what _not_ to do, so we need to get their attention when reading about "clone -s". For (2), we are telling them how git-repack can be used to accomplish a task, but until they know that git-repack is the right tool, they have no reason to look at the repack documentation. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-filter-branch.txt')
0 files changed, 0 insertions, 0 deletions