Defect #13311
In repository view, git commits are ordered by date, not by commit orders
Status: | Closed | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | SCM | |||
Target version: | - | |||
Resolution: | Duplicate | Affected version: | 2.2.2 |
Description
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 1.7.11.3
Related issues
History
#1
Updated by Toshi MARUYAMA over 9 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Duplicate with #5357.