From: Jeff King <peff@peff.net>
To: Derrick Stolee <stolee@gmail.com>
Cc: Thomas Braun <thomas.braun@virtuell-zuhause.de>,
Taylor Blau <me@ttaylorr.com>,
GIT Mailing-list <git@vger.kernel.org>,
Derrick Stolee <dstolee@microsoft.com>
Subject: Re: 2.29.0.rc0.windows.1: Duplicate commit id error message when fetching
Date: Fri, 9 Oct 2020 13:55:06 -0400 [thread overview]
Message-ID: <20201009175506.GA957408@coredump.intra.peff.net> (raw)
In-Reply-To: <64de22fd-2e1b-aaab-3a8e-f6f1d630a46e@gmail.com>
On Fri, Oct 09, 2020 at 01:46:07PM -0400, Derrick Stolee wrote:
> > Can you reproduce it if you do
> >
> > git config core.commitGraph false
> > git config fetch.writeCommitGraph true
> > ?
>
> I _can_ repro it in this case! I think there must be something
> very interesting going on where the commit-graph is parsed in
> _some_ places, but not in others. This is something that I can
> really start to dig into.
Here's a much more minimal reproduction:
git init repo
cd repo
git commit --allow-empty -m one
git rev-parse HEAD |
git -c core.commitGraph=false \
commit-graph write --split=no-merge --stdin-commits
git rev-parse HEAD |
git -c core.commitGraph=false \
commit-graph write --split=no-merge --stdin-commits
git commit --allow-empty -m two
git rev-parse HEAD |
git commit-graph write --split --stdin-commits
The final write will die() with the "unexpected duplicate" message.
-Peff
next prev parent reply other threads:[~2020-10-09 17:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 20:28 2.29.0.rc0.windows.1: Duplicate commit id error message when fetching Thomas Braun
2020-10-07 21:06 ` Jeff King
2020-10-08 9:52 ` Thomas Braun
2020-10-08 12:06 ` Jeff King
2020-10-08 12:50 ` Derrick Stolee
2020-10-08 13:22 ` Derrick Stolee
2020-10-09 15:29 ` Thomas Braun
2020-10-09 16:49 ` Derrick Stolee
2020-10-09 17:12 ` Thomas Braun
2020-10-09 17:46 ` Derrick Stolee
2020-10-09 17:55 ` Jeff King [this message]
2020-10-09 18:28 ` Taylor Blau
2020-10-09 18:33 ` Derrick Stolee
2020-10-09 18:37 ` Taylor Blau
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=20201009175506.GA957408@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=stolee@gmail.com \
--cc=thomas.braun@virtuell-zuhause.de \
/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.