Opened 17 years ago
Last modified 5 years ago
#3177 new enhancement
Don't show non-merge revisions
Reported by: | gregmac | Owned by: | Emmanuel Blot |
---|---|---|---|
Priority: | lowest | Component: | RevtreePlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
This plugin would be much more useful if it was possible to not show the in-between revisions, and just show the ones where merges were taking place, as well as the first/last revisions of a branch (just for completeness).
For example, on the following image:
under branches/t810b, revisions 2623, 2628, 2632, and 2633 should not be displayed; 2621, 2622 shouldn't be shown for t1093b.
This would making viewing a repository with many revisions much more useful. For example, we often have 15 or 20 commits before doing a merge - particularly on trunk where many of the commits do not get merged. When you do a revtree of the last couple hundred commits, you get a huge long list where you can't even see both ends of the merge lines without scrolling, effectively making the chart useless.
Attachments (0)
Change History (6)
comment:1 Changed 17 years ago by
comment:2 Changed 16 years ago by
Priority: | normal → lowest |
---|
No feedback from user.
It seems not to be a trivial change, while no other users have requested this feature: decreasing priority till other voices are raised to implement it.
comment:3 Changed 16 years ago by
Cc: | ryano@… added; anonymous removed |
---|
comment:4 Changed 15 years ago by
Cc: | Ryan J Ollos added; ryano@… removed |
---|
comment:5 Changed 15 years ago by
I would like to raise a voice about this feature. The software my team has been developing for the past years now has over 25,000 revisions spread across multiple branches. When I first heard of this plugin, I thought it would help me to manage the branches, but having pages upon pages of "in-between source revisions" prevents the plugin from being usable for us, and being able to hide those revisions would be a great improvement.
comment:6 Changed 5 years ago by
Cc: | Ryan J Ollos removed |
---|
Replying to gregmac:
Well, the "useful"ness is somewhat subjective, but if I understand it right you want to be able to hide in-between source revisions in a merge operation - knowing that's it's simply about hiding revisions, as the revisions do get merge anyway into the destination changeset.
Is that what you'd like?