This probably boils down to personal preference (and bikeshed! ;), but commits are currently listed from most recent to most ancient. This is the same as in a git log... but I'm not sure that's the way people expect them to be. I've been doing them oldest to newest in my release notes so far.

CommentFileSizeAuthor
#5 option-for-commits-in-reverse-order-1253366.patch2 KBpetsagouris
#3 option-for-commits-in-reverse-order-1253366.patch1.96 KBpetsagouris

Comments

Grayside’s picture

Grayside commented

I prefer oldest to newest for commits myself, as it allows you to see the evolution of a release. Maybe an option to determine the sort order?

petsagouris’s picture

petsagouris commented
Category: bug » feature
petsagouris’s picture

petsagouris commented
Assigned: Unassigned » petsagouris
Status: Active » Needs review
StatusFileSize
new option-for-commits-in-reverse-order-1253366.patch1.96 KB

Ok, I went ahead and added the '--reverse' option. Please review.

Grayside’s picture

Grayside commented
Status: Needs review » Needs work

Description of reverse parameter should indicate what "normal" is. Tempted to say the parameter should be --order=asc/desc but that may be overly verbose.

petsagouris’s picture

petsagouris commented
StatusFileSize
new option-for-commits-in-reverse-order-1253366.patch2 KB

Since this is about git, the "normal" is set by the git system.
I can see your point though. Would you like to go about a more descriptive line for that description?

petsagouris’s picture

petsagouris commented
Status: Needs work » Needs review
petsagouris’s picture

petsagouris commented
Title: commits in the wrong order? » Provide options for showing commits from old to new
Grayside’s picture

Grayside commented
Status: Needs review » Fixed

http://drupalcode.org/project/grn.git/commit/647022b

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.