Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 340693

Summary:

History rendered incorrectly

Product:

[Technology] EGit

Reporter:

Matthias Sohn <matthias.sohn>

Component:

Assignee:

Christian Halstrick <christian.halstrick>

Status:

CLOSED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

bugzilla-eclipse, christian.halstrick, robin

Version:

0.12

Target Milestone:

---

Hardware:

OS:

Mac OS X

Whiteboard:

Attachments:

Description	Flags
git bundle containing sample repository showing the problem	none
screenshot of wrongly rendered history	none

Description Matthias Sohn

2011-03-22 14:13:36 EDT

The history for the attached repository is rendered incorrectly (see screenshot)

org.eclipse.egit (0.12.0.201103170411)
org.eclipse.jgit (0.12.0.201103161124)

Comment 1 Matthias Sohn

2011-03-22 14:14:29 EDT

Created attachment 191705 [details]
git bundle containing sample repository showing the problem

Comment 2 Matthias Sohn

2011-03-22 14:15:07 EDT

Created attachment 191706 [details]
screenshot of wrongly rendered history

Comment 3 Marcus Bleil

2012-02-01 04:19:54 EST

Hello you all,
we have exactly the same mistake like the screenshot shows: a branch that goes to infinity.

Marcus

Comment 4 Stefan Lay

2012-06-27 06:05:04 EDT

I downloaded the bundle but could not close from it:

$ git clone egit-training.bundle egit-training.test
Cloning into egit-training.test...
warning: remote HEAD refers to nonexistent ref, unable to checkout.

$ cd egit-training.test/

$ git log
fatal: bad default revision 'HEAD'

Comment 5 Stefan Lay

2012-06-27 07:34:53 EDT

I meant: I downloaded the bundle but could not **clone*** from it:

Comment 6 Christian Halstrick

2012-07-04 10:42:33 EDT

This repository contained a commit with duplicate parents. Commit 74efda contained two times c8c432 as parent. This irritated EGit history view. A fix was proposed in https://git.eclipse.org/r/#/c/6592/. If this fix get's accepted this bug can be closed. Please review.

Comment 7 Robin Stocker

2013-09-27 14:08:41 EDT

The patch has been merged, closing as fixed.