Edgewall Software
Modify

Opened 17 years ago

Closed 17 years ago

Last modified 17 years ago

#5819 closed defect (fixed)

Timeline events with same exact date show up backwards

Reported by: Tim Hatch Owned by: Tim Hatch
Priority: normal Milestone: 0.11
Component: timeline Version: devel
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

I've encountered this using external tools to modify svn repositories. When the timestamps are the same second, revisions are displayed newest-last in the timeline.

I'm attaching a fix that works for me. I'm not using any esoteric timeline event providers, so I'd just like some verification this doesn't break anything for other users.

Attachments (1)

timeline-reversed.diff (566 bytes ) - added by Tim Hatch 17 years ago.
Diff against r5887

Download all attachments as: .zip

Change History (5)

by Tim Hatch, 17 years ago

Attachment: timeline-reversed.diff added

Diff against r5887

comment:1 by Tim Hatch, 17 years ago

Resolution: fixed
Status: newclosed

After discussing with Coderanger a bit on IRC, he pointed out this was actually an issue with the svn backend generating changesets in the wrong order. get_changesets() should generate changes in reverse-chronological order, and the sort done at the timeline level should leave alone whatever order that is in case of a tie on timestamp.

Hopefully fixed in r5891

comment:2 by Emmanuel Blot, 17 years ago

How this ticket relates to #5153?

comment:3 by Tim Hatch, 17 years ago

Nice catch, I didn't notice that ticket even with searching. In my case they were committed to a tweaked repository using another vcs so they had exactly the same timestamp, and still triggered the #5153 issue even with its fix. r5891 makes the get_changesets order start with youngest_rev first, which is consistent with the order we'd like them to display in the timeline (in case of exact ties…).

in reply to:  3 comment:4 by Emmanuel Blot, 17 years ago

Replying to thatch:

In my case they were committed to a tweaked repository using another vcs so they had exactly the same timestamp, and still triggered the #5153 issue even with its fix. r5891 makes the get_changesets order start with youngest_rev first, which is consistent with the order we'd like them to display in the timeline (in case of exact ties…).

Ok, thanks for the details.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Tim Hatch.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Tim Hatch to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.