diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-10-18 11:28:28 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-10-18 11:28:28 -0400 |
| commit | 6d47996066dd7045eedfbf398580156cc49c4b31 (patch) | |
| tree | d4e1d16511d18e40a82cd2bfd9e1efe500465e31 | |
| parent | 591ac350c7e9dff8ace565096468932d7be556a2 (diff) | |
followup
| -rw-r--r-- | doc/forum/how_to_disaster_recovery/comment_6_e8ec7b1fbbb81d61d06a7def61b06354._comment | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/forum/how_to_disaster_recovery/comment_6_e8ec7b1fbbb81d61d06a7def61b06354._comment b/doc/forum/how_to_disaster_recovery/comment_6_e8ec7b1fbbb81d61d06a7def61b06354._comment new file mode 100644 index 000000000..425558b25 --- /dev/null +++ b/doc/forum/how_to_disaster_recovery/comment_6_e8ec7b1fbbb81d61d06a7def61b06354._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 6""" + date="2016-10-18T15:27:05Z" + content=""" +Another user reported the same problem. Their repo indeed had a tree object +that contained two items with the same name. In this case, two trees, +with different contents. + + 040000 tree cd854aba649cee8855ec72579f4c98100471f7cf Dokument + 040000 tree 1ae499997746c8e976cf02edc2276532978dafc5 Dokument + +This user had been using adjusted branches, which would be my lead suspect. + +Original reporter, did you use git-annex's adjusted branches feature. +"""]] |