summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89 <John@web>2013-08-28 03:22:46 +0000
committerGravatar admin <admin@branchable.com>2013-08-28 03:22:46 +0000
commitd3cf567f7217ba8a0e522886d410a350dbc9e20c (patch)
treef340c098a84f637ebb8bfc2c7202c8bc1d41f347
parentf9ed14d326dd8352fbb17377280cfef11c07f539 (diff)
-rw-r--r--doc/forum/Pruning_out_unwanted_Git_objects.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/Pruning_out_unwanted_Git_objects.mdwn b/doc/forum/Pruning_out_unwanted_Git_objects.mdwn
new file mode 100644
index 000000000..36397b267
--- /dev/null
+++ b/doc/forum/Pruning_out_unwanted_Git_objects.mdwn
@@ -0,0 +1,3 @@
+I have a backups repository with a few files in it, that at one point had some huge filesets erroneously added to it. As a result, even though there are only 23,334 annexed files, the number of non-dangling Git objects in the repository comes to 593,584.
+
+Normally I would use `git filter-branch` to clear out the deadwood in situations like this, since it is a completely private repository. What I'm wondering is, is any such thing possible with git-annex, or is the best option just to start over, copy all the files into the new repository, and then `git-add` them all?