diff options
author | http://joeyh.name/ <http://joeyh.name/@web> | 2014-03-10 18:12:29 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2014-03-10 18:12:29 +0000 |
commit | dd6ffbf296a9146ea4f3e3dc3a4010f05aa6b3ee (patch) | |
tree | 6fef934f50fc3950843da435092d0df1a78c2d7b | |
parent | b590db53ef36f9446d32cf29423b658697cdf6b7 (diff) |
Added a comment
-rw-r--r-- | doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment b/doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment new file mode 100644 index 000000000..fa437311f --- /dev/null +++ b/doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 8" + date="2014-03-10T18:12:29Z" + content=""" +In a quick test with a 32 mb dummy fsck output, git-repair ballooned up to 1.7 gb. Clearly something not happy there, although in my case this did not cause it to crash. +"""]] |