From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "Dominy\, Patrick A" <patrick-dominy@uiowa.edu>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git fsck finds duplicate entries
Date: Wed, 29 May 2019 00:48:50 +0200 [thread overview]
Message-ID: <87d0k2mbzh.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <2FFF873C-0FCB-4E5F-BEA2-BCE54A623D1E@uiowa.edu>
On Tue, May 28 2019, Dominy, Patrick A wrote:
> Hi,
> Running git fsck against one of our repositories yields the following:
> Error in tree xxxxxxx: duplicateEntries: contains duplicate file entries
>
> 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.
> The commit that introduced the issue happened some time ago, making going back to the bad commit and replaying the commits a daunting task.
> Any suggestions would be much appreciated.
At this point you either rewrite the repository or live with it. To live
with it see the fsck.skipList documentation in git-config(1). I.e. you'd
whitelist this tree as known-bad.
prev parent reply other threads:[~2019-05-28 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 21:42 git fsck finds duplicate entries Dominy, Patrick A
2019-05-28 22:48 ` Ævar Arnfjörð Bjarmason [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0k2mbzh.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=patrick-dominy@uiowa.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.