-
Notifications
You must be signed in to change notification settings - Fork 762
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
Use git log -m, and handle octopus merges too #3167
Conversation
Also: - Add FileHistoryCacheOctopusTest showing dupes for merges (before revising for this patch) - Update parsing of Git revision with labels - Fix oracle#3166 "partial parse of git log"
Pull Request Test Coverage Report for Build 5206
💛 - Coveralls |
What happens when diffing a merge changeset and regular changeset in history view ? |
Also, seems like there are some Windows build failures related to the changes. |
@vladak , it's no different from any other diff. Reminder that OpenGrok starts two processes (in parallel thanks to #2955) to get the diff data for the two commit hashes. A merge has a commit hash too. Also I pushed a change that hopefully fixes the Windows build. |
Sounds good. Thanks ! |
I think this touches also #1167, @idodeclare do you think this resolves it? |
@tulinkry, yes I think it does. |
Thanks, closing the issue |
Hello,
Please consider for integration this patch to use the
-m
switch withgit log
to support octopus merges as well as to properly report if new files come into existence during a merge.(This is an extract from a branch of mine actually named
bugfix/git_parsing
from last year which I realize now was intended at first to support the above but where I had gone down a deep rabbit hole trying to speed up history for the FreeBSD repo and arrived at several time-consuming but lackluster results. I put the branch on the back burner forgetting its original purpose.)Users will not be forced to reindex, but any merge history previously hidden will require a reindex to be visible.
Thank you.