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.
Related to #9796
Proposed changes
It is possible to configure the following in FormFileHistory, but the settings also affect the normal git-log.
The effect on normal git-log is not great, but it is there.
https://git-scm.com/docs/git-log#Documentation/git-log.txt---full-history
https://git-scm.com/docs/git-log#Documentation/git-log.txt---simplify-merges
If View had a submenu, they could be put there (but one submenu with two items is not much gain).
This could also be in Settings, similar to above.
Something should be put in the doc as well, probably here (in the 4.0 PR draft).
There are quite some things that should be added to the doc though, I will not do all of that.
https://git-extensions-documentation.readthedocs.io/en/feature-4.0-prepare/browse_repository.html#main-toolbar
gitextensions/GitExtensionsDoc#140
Screenshots
Before
This is not changed
RevGrid context menu in FileHistory, removed as they are added to View.
After
FormBrowse
All RevGrid View menus
Test methodology
Manual
Merge strategy
I agree that the maintainer squash merge this PR (if the commit message is clear).
✒️ I contribute this code under The Developer Certificate of Origin.