Defect #13311

In repository view, git commits are ordered by date, not by commit orders

Added by Ji Oh Yoo over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:Duplicate Affected version:2.2.2


One of my colleges had error in his OS time settings, so his commits had future timestamp than other commits.

In repository, the graph and the order of commits is the following:

Steve Jinhwan Choi's 2 commits are affected, and for example,
his commit fef55f16 must be a parent the commit 607d5d4f.

If I click the revision, then the revision page then shows the correct information:

Revision fef55f16
ID    fef55f1652facbffd9e912e085ce3f9c409a2b07
Parent    d0748b7b, bc93c2d4
Child    607d5d4f

My Redmine related settings:

Ruby version              1.9.3 (x86_64-linux)
RubyGems version          1.8.24
Rack version              1.4
Rails version             3.2.11
Environment               production
Database adapter          mysql2
git version

repo.png (72.2 KB) Ji Oh Yoo, 2013-02-28 06:50

Related issues

Duplicates Redmine - Defect #5357: Git: SCM revisions ordered by date/time (should be revers... New 2010-04-20


#1 Updated by Toshi MARUYAMA over 9 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Duplicate with #5357.

Also available in: Atom PDF