file history improvements
1) highlight the current file revision in the history list GUI & command line as selected by the workspace (I had a feeling it was bold but isn't in 5.0.44.581). If the workspace revision is modified, the parent should still be highlighted.
2) give an indication of which revisions have been merged in the history list (eg. a column for number of branches seeing this revision; merged yes/no)
3) populate the 'Properties' panel when selecting items in the 'Version tree' (it is blank regardless of which branch or cs I select, and many of the cs numbers and names on short branches are illegible)
See also
http://plasticscm.uservoice.com/forums/15467-general/suggestions/3950398-show-merges-in-file-history-and-2d-history
I assume 'done' here referes to the version tree?
robl
shared this idea
-
Göran Wallgren
commented
Hi robl, not sure if this is what you were seeing but I got hundreds of "U" changesets in 2D History Tree by accidentally unchecking "Display only relevant changesets" which is linked to the slightly hidden settings under the "Version tree" vertical tab inside the "Options" sidebar in 2D History Tree. This is in v5.4.16.
-
Piotr Mis
commented
I also see "History" and "History tree" pretty confusing.
Maybe at least blog post which would deeply explain all relations and markers on History tree?
-
robl
commented
4) an option to filter the history list to only show ancestors of the current revision
5) option to only draw the the revision changesets on the item version tree (ie. an ancestor graph) -
robl
commented
Hi, yes I understand there is a difference between changesets and revisions but am not clear why all the 'U' changesets are necessary.
eg. if a file only contains 4 revisions, why are there many more 'U' changesets (>100) than visible branches (~20)? Even with 'display only relevant changesets', there are many U's with connected only to changesets on the same branch. The 4 revisions appear in 'A' and 'C' changesets. There are also 'A(Me)' changesets. These labels aren't described in the legend.
What I would really like to see is a minimal diagram clearly highlighting the actual revisions with very little else. Not sure how possible this is though. Otherwise some functionality to search for all the actual revision changesets would help.
-
Hi Robl,
Do you know why we show the "U" marked revisions, correct?
The thing is that the merges happen between changesets, not between revisions, and hence you can be merging changeset 104 which contains a revision from file 'foo.c' which was created in cset 100, and then 101, 102, 103 and 104 are marked with a "U" because the file wasn't modified there, but the merge happens between 104 and the destination cset. Is that clear?
-
robl
commented
The version tree contains many hundreds more changesets than the history list with many of them marked 'U'. Even displaying only relevant changesets and filtering out other people's branches the diagram is very noisy and difficult to use.
