From: Jonathan Tan <jonathantanmy@google.com>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org, stolee@gmail.com,
Jonathan Tan <jonathantanmy@google.com>
Subject: Commit graph chains with no corresponding files?
Date: Mon, 29 Jun 2020 15:07:43 -0700 [thread overview]
Message-ID: <20200629220744.1054093-1-jonathantanmy@google.com> (raw)
At $DAYJOB, a few people have reported "warning: unable to find all
commit-graph files" warnings. Their commit-graph-chain files have a few
lines, but they only have one commit graph file with very few commits. I
suspected something happening during fetch, because (as far as I know) a
fetch may cause an incremental commit graph to be written, but I ran a
fetch on a large repository myself and didn't run into this problem.
Has anyone ran into this problem before, and know how to reproduce?
next reply other threads:[~2020-06-29 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 22:07 Jonathan Tan [this message]
2020-06-30 1:51 ` Commit graph chains with no corresponding files? Derrick Stolee
2020-07-16 22:57 ` [FYI] commit-graph: trace expiry of commit graph links Jonathan Tan
2021-02-25 4:54 ` Commit graph chains with no corresponding files? Bryan Turner
2021-02-25 14:20 ` Derrick Stolee
2021-02-27 2:49 ` Bryan Turner
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=20200629220744.1054093-1-jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--cc=stolee@gmail.com \
/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.