Bug 224403 - Use of a tree in the History view for revisions
Summary: Use of a tree in the History view for revisions
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-27 11:59 EDT by utilisateur_768 CLA
Modified: 2019-09-06 16:17 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description utilisateur_768 CLA 2008-03-27 11:59:15 EDT
Build ID: I20080207-1530

It would be great if you could use a tree to represent the revisions branching in the "History" view. Selecting revisions in a specific branch would be easier because mixing all the revisions can be confusing.

Only the "revision" column would need changes.

Thanks
Comment 1 Tomasz Zarna CLA 2008-03-28 06:27:27 EDT
Sounds like a great idea indeed. I'm not sure if you thought about it the same way, but I would simply replace current "This Month/Older than This Month" groups with something like "HEAD/<branch1>/<branch2>" or "Current Branch/HEAD/<branch1>" (if you're currently on <branch2>). To be clear here, I would add an option two switch between these two grouping options (by date and by branch), not replace the current one.

That said, I think we should also take a look at bug 76386 or even mark it as a dupe.

Utilisateur, have you thought about making a patch? I'm eager to help you with it.
Comment 2 Olexiy Buyanskyy CLA 2009-07-02 14:22:13 EDT
I think screen shot can be useful

http://bitbucket.org/mercurialeclipse/main/wiki/Screenshots

We can use the same graph column.

Plus you may need to look in

http://versiontree.sourceforge.net/
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:17:12 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.