From 524b4efba56a9a8615ec54a4ff9b33daf62059f5 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 11 May 2017 12:35:34 -0400 Subject: comment --- ...omment_1_654527ef2350fe871e2d7ff6addc6713._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/tips/splitting_a_repository/comment_1_654527ef2350fe871e2d7ff6addc6713._comment (limited to 'doc/tips/splitting_a_repository') diff --git a/doc/tips/splitting_a_repository/comment_1_654527ef2350fe871e2d7ff6addc6713._comment b/doc/tips/splitting_a_repository/comment_1_654527ef2350fe871e2d7ff6addc6713._comment new file mode 100644 index 000000000..3c04c2061 --- /dev/null +++ b/doc/tips/splitting_a_repository/comment_1_654527ef2350fe871e2d7ff6addc6713._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-05-11T16:28:32Z" + content=""" +This is a simple way to split a repository, but the resulting split git +repository will be larger than is really necessary. + +When you `dropunused` all the hard links that are not present in the +repository, git-annex will commit a log to the git-annex branch saying "I +don't have this content" for each of them. That seems unnecessary since +it probably does not have an earlier log saying it contained the content +that was hard linked into it, and perhaps could be improved in git-annex +to not record that unncessarily, but that's what it does currently. + +So I suggest running `git annex forget` after the dropunused or at some +later point. That will delete all traces of those log files from +the git-annex branch. +"""]] -- cgit v1.2.3