{"thread":{"id":"51191","subject":"git fsck finds duplicate entries","startedAt":"2019-05-28T21:42:56Z","lastAt":"2019-05-28T22:48:55Z","messageCount":2,"participants":["Dominy, Patrick A","Ævar Arnfjörð Bjarmason"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"376364","messageId":"2FFF873C-0FCB-4E5F-BEA2-BCE54A623D1E@uiowa.edu","threadId":"51191","inReplyTo":null,"subject":"git fsck finds duplicate entries","fromName":"Dominy, Patrick A","fromEmail":"patrick-dominy@uiowa.edu","sentAt":"2019-05-28T21:42:52Z","receivedAt":"2019-05-28T21:42:56Z","isPatch":false,"sender":{"key":"patrick-dominy@uiowa.edu","avatar":null},"body":"Hi,\nRunning git fsck against one of our repositories yields the following:\nError in tree xxxxxxx: duplicateEntries: contains duplicate file entries\n \nWe are struggling with the best approach to resolve the issue.  We’ve used git replace, which successfully creates the replace reference, but fsck still returns the same duplicate entry error.\nThe commit that introduced the issue happened some time ago, making going back to the bad commit and replaying the commits a daunting task.\nAny suggestions would be much appreciated.\n \nThanks\n\n"},{"id":"376370","messageId":"87d0k2mbzh.fsf@evledraar.gmail.com","threadId":"51191","inReplyTo":"2FFF873C-0FCB-4E5F-BEA2-BCE54A623D1E@uiowa.edu","subject":"Re: git fsck finds duplicate entries","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2019-05-28T22:48:50Z","receivedAt":"2019-05-28T22:48:55Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Tue, May 28 2019, Dominy, Patrick A wrote:\n\n> Hi,\n> Running git fsck against one of our repositories yields the following:\n> Error in tree xxxxxxx: duplicateEntries: contains duplicate file entries\n>\n> We are struggling with the best approach to resolve the issue.  We’ve used git replace, which successfully creates the replace reference, but fsck still returns the same duplicate entry error.\n> The commit that introduced the issue happened some time ago, making going back to the bad commit and replaying the commits a daunting task.\n> Any suggestions would be much appreciated.\n\nAt this point you either rewrite the repository or live with it. To live\nwith it see the fsck.skipList documentation in git-config(1). I.e. you'd\nwhitelist this tree as known-bad.\n"}]}