Ensure that git commit tree continues properly over the page #12142
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Andrew Thornton <[email protected]>
Signed-off-by: Andrew Thornton <[email protected]>
lafriks
approved these changes
Jul 4, 2020
GiteaBot
added
the
lgtm/need 1
Signed-off-by: Andrew Thornton <[email protected]>
9 tasks
mrsdizzie
approved these changes
Jul 16, 2020
GiteaBot
added
lgtm/done
|
🚀 |
|
🚀 |
i haven't tried this, but i have a repo with over 80,000 commits. does this scale? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One of the problems with using
git log --graph --skip=$n -n $nis that branches that continue across pages disappear. This PR does a slightly different solution - the whole graph is generated but only the last$ncommits are collected - (including any intervening relations)Fix #12133
Fix #10217
Signed-off-by: Andrew Thornton [email protected]