summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-03-26 12:07:44 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-03-26 12:07:44 -0400
commit3d016ab66012393fef81f8df062b1228c36ac0e2 (patch)
treefe469e4b4a37620553ba484bb01748666c81d67d
parent904b82358e3b0676d13525c324bcefb108f33db8 (diff)
add
-rw-r--r--doc/bugs/git_pack-objects_eats_all_teh_ram/comment_2_77cb32e7cee99d7325e7c6a595844e0c._comment15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/bugs/git_pack-objects_eats_all_teh_ram/comment_2_77cb32e7cee99d7325e7c6a595844e0c._comment b/doc/bugs/git_pack-objects_eats_all_teh_ram/comment_2_77cb32e7cee99d7325e7c6a595844e0c._comment
new file mode 100644
index 000000000..07ff19070
--- /dev/null
+++ b/doc/bugs/git_pack-objects_eats_all_teh_ram/comment_2_77cb32e7cee99d7325e7c6a595844e0c._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2015-03-26T15:50:49Z"
+ content="""
+git-annex never directly calls `git pack-object` or `git repack`
+or anything like that. This is likely being done internally by git,
+as controlled by `gc.auto` configuration.
+
+If this is eating a lot of ram, it seems to me that you have likely
+checked some large files into you git repository, rather than using
+git-annex to manange them. git using lots of ram when large
+files have been added to it is one of the reasons git-annex exists,
+after all..
+"""]]