Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365274 - Wrong line in History View Graph
Summary: Wrong line in History View Graph
Status: RESOLVED FIXED
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 1.1   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-01 03:05 EST by Peter Kullmann CLA
Modified: 2011-12-06 04:39 EST (History)
2 users (show)

See Also:

Attachments
Screenshot of the graph with the invalid lines (75.27 KB, image/png)
2011-12-01 03:10 EST, Peter Kullmann CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Kullmann CLA 2011-12-01 03:05:50 EST 
The graph is showing lines conncting unrelated commits. See the attached screen shot.
Comment 1 Peter Kullmann CLA 2011-12-01 03:10:41 EST 
Created attachment 207776 [details]
Screenshot of the graph with the invalid lines

The selected commit has only one parent. The graph shows two parents which is wrong. It should only show the green line to the right. Also it has no children. 

Another way to state the same: The dot representing the selected commit should be drawn on its own and not on the line for branch R2_3_maintenance.
Comment 2 Christian Halstrick CLA 2011-12-05 19:08:31 EST 
Could you please try again with latest nightly build. Change http://egit.eclipse.org/r/#change,4719 should have solved this issue.
Comment 3 Peter Kullmann CLA 2011-12-06 02:02:11 EST 
I'm afraid my repository evolved in the meantime and doesn't show the problem right now.
Comment 4 Christian Halstrick CLA 2011-12-06 04:39:18 EST 
I know, younger commits influence how older ones are presented. Means: if you see a rendering problem at one point in time it may vanish if the repo evolves.

I'll close this bug now. The latest fix seems to fit to your problem. You can reopen if you see the bug again.