New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Be clear why commit-graph was skipped #875
Conversation
When `gc.writeCommitGraph = true`, it is possible that the commit-graph is _still_ not written: replace objects, grafts and shallow repositories are incompatible with the commit-graph feature. Under such circumstances, we need to indicate to the user why the commit-graph was not written instead of staying silent about it. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
/submit |
Submitted as pull.875.git.1613057954213.gitgitgadget@gmail.com To fetch this version into
To fetch this version to local tag
|
On the Git mailing list, Derrick Stolee wrote (reply to this):
|
User |
On the Git mailing list, Junio C Hamano wrote (reply to this):
|
This branch is now known as |
This patch series was integrated into seen via git@153cd96. |
This patch series was integrated into seen via git@dabbcfd. |
This patch series was integrated into next via git@e9faad5. |
This patch series was integrated into seen via git@726b11d. |
This patch series was integrated into next via git@726b11d. |
This patch series was integrated into master via git@726b11d. |
Closed via 726b11d. |
On the Git mailing list, Ævar Arnfjörð Bjarmason wrote (reply to this):
|
User |
After repairing my local checkout, I was puzzled that the commit-graph file was not written. Turns out that I still had almost a dozen replace objects. But I only found out that they were blocking the commit-graph when I stepped through
git gc
in a debugger. This is my attempt to make it more straight-forward to recover from similar situations in the future.Cc: Derrick Stolee dstolee@microsoft.com
cc: Derrick Stolee stolee@gmail.com
cc: Ævar Arnfjörð Bjarmason avarab@gmail.com