After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 777969 - Reordering commits leads to wrong graph display
Reordering commits leads to wrong graph display
Status: RESOLVED DUPLICATE of bug 619211
Product: gitg
Classification: Applications
Component: gui
3.17.x
Other Linux
: Normal normal
: ---
Assigned To: gitg-maint
gitg-maint
Depends on:
Blocks:
 
 
Reported: 2017-01-31 08:07 UTC by Bruce Merry
Modified: 2017-09-30 20:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Example repository (8.82 KB, application/x-bzip)
2017-01-31 08:07 UTC, Bruce Merry
Details
Screenshot (44.02 KB, image/png)
2017-01-31 08:10 UTC, Bruce Merry
Details

Description Bruce Merry 2017-01-31 08:07:41 UTC
Created attachment 344629 [details]
Example repository

This could be intended behaviour, but I found it very confusing.

It appears that having a linear history where the order of timestamps doesn't match the topological order causes the graph view to display incorrectly. This could happen with interactive rebasing or with cherry-picking.

To reproduce:
1. Create a new repository and create 4 arbitrary commits (each on a different file to avoid conflicts during rebasing).
2. Do 'git rebase -i HEAD~3' and swap the order of commits 2 and 3, so that the history is now 1, 3, 2, 4.
3. Do 'git branch HEAD~1 mybranch' so that mybranch references commit 3.
4. Run 'gitg --all'.

The history appears as two separate streams (commits 2 and 4 in one stream, commits 1 and 3 in the other). I'll attach a screenshot. Running just gitg (without --all) shows the correct history, as does "show history in topological order".
Comment 1 Bruce Merry 2017-01-31 08:10:14 UTC
Created attachment 344630 [details]
Screenshot
Comment 2 Alexandre Franke 2017-09-30 20:46:01 UTC

*** This bug has been marked as a duplicate of bug 619211 ***