The man gitk at least mentions it does take the same options than git rev-list, including
--date-order
This option is similar to
--topo-orderin the sense that no parent comes before all of its children, but otherwise things are still ordered in the commit timestamp order.
See "Guide to understanding gitk?" for more.
Note: if -d or --date-order is really the argument you are after, better not using too much, according to Linus himself (from lists-archives.com/git or www.spinics.net/lists/git/):
The thing is,
--date-orderstrings out and mixes up the commits on the same development chain, and by doing so it makes the different chains of development much harder to see.
It also ends up showing the development in a more "parallel" way, which in turn makes the view even harder to read.So I would suggest not using
--date-orderby default. It doesn't add anything to any normal flow, and it makes the big picture harder to see.The only time you really want
--date-order(or "-d", which is shorthand for it for justgitk) is really
- when the big picture is really really simple, and you actually want to see more detail because the big picture is too trivial to even be interesting otherwise.
(In other words:--date-orderis fine for