Context Navigation

Modify ↓

#11481 closed enhancement (duplicate)

Witness the followed set of rebased changesets: timeline:2014-02-10T0048

They're coming up backwards:

When they should come in reverse chronological order (i.e. most recent first):

So in case of a tie in the git-committer date, we should use the git-author date as a second key.

Maybe a duplicate of #11467?

Looks like ;-) Sorry for the noise!

Change Properties

Summary:
Description:	Witness the followed set of rebased changesets: timeline:2014-02-10T0048 They're coming up backwards: - //Initial code drop, with PEP-0008 changes and inherit// - //Show count in `h2`// - ... - //Allow the rendering method to be specified by the request handler// When they should come in reverse chronological order (i.e. most recent first): - //Allow the rendering method to be specified by the request handler// - ... - //Show count in `h2`// - //Initial code drop, with PEP-0008 changes and inherit// So in case of a tie in the `git-committer` date, we should use the `git-author` date as a second key. You may use WikiFormatting here.
Type:		Priority:
Milestone:		Component:
Version:		Severity:
Keywords:		Cc:	Set your email in Preferences
Branch:
Release Notes:
API Changes:
Internal Changes:

Action

leave as closed The ticket will remain with no owner.

reopen The resolution will be deleted. Next status will be 'reopened'.

change ownership to The owner will be changed from (none) to the specified user.

Your email or username:

E-mail address and name can be saved in the Preferences .

You may use WikiFormatting here.

Attachments ↑ Description ↑

Note: See TracTickets for help on using tickets.