From 7e317bcf039d195de3d3c003758504ac6a67fdb8 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Thu, 19 Sep 2013 18:53:14 +0000 Subject: [PATCH] Added a comment --- ...comment_3_9f83ef190547b291a715cda55b7977d4._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_3_9f83ef190547b291a715cda55b7977d4._comment diff --git a/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_3_9f83ef190547b291a715cda55b7977d4._comment b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_3_9f83ef190547b291a715cda55b7977d4._comment new file mode 100644 index 0000000000..11f03b39d9 --- /dev/null +++ b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_3_9f83ef190547b291a715cda55b7977d4._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.14.105" + subject="comment 3" + date="2013-09-19T18:53:14Z" + content=""" +I just fixed a memory leak that occurred when large files were checked directly into git (perhaps by accident by committing files manually when using direct mode). However, I don't think it affected `git annex merge`. + +Still need information about how to reproduce this bug... +"""]]