aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2014-01-06 16:14:30 +0000
committerGravatar admin <admin@branchable.com>2014-01-06 16:14:30 +0000
commite5417e3a7c5b1836b0c3909230139a72dc00da2e (patch)
treee20ab0e607a88288dd4afe5b28cd53d822dac53f
parent064447cdc053b6d4381fe1c89c53cfa15db8b3ab (diff)
Added a comment
-rw-r--r--doc/bugs/fatal:_git-write-tree:_error_building_trees/comment_2_77295c0b749e984a6fb200d3b73b5765._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/fatal:_git-write-tree:_error_building_trees/comment_2_77295c0b749e984a6fb200d3b73b5765._comment b/doc/bugs/fatal:_git-write-tree:_error_building_trees/comment_2_77295c0b749e984a6fb200d3b73b5765._comment
new file mode 100644
index 000000000..dabc1d4f3
--- /dev/null
+++ b/doc/bugs/fatal:_git-write-tree:_error_building_trees/comment_2_77295c0b749e984a6fb200d3b73b5765._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.35"
+ subject="comment 2"
+ date="2014-01-06T16:14:29Z"
+ content="""
+As far as I can tell from git's code, this involves a \"cache-tree\" data structure stored in git's index file. git-annex has nothing to do with writing index files, beyond running git plumbing. So I don't see how this could be anything other than a corrupt index file (of a sort that git fsck doesn't detect), or a git bug. The best thing to do would be to send an example of a repository having this problem to the git developers for analysis.
+"""]]