{"thread":{"id":"33956","subject":"Feature-request: Ordering `git log --graph` based on *author's* timestamp","startedAt":"2013-05-28T09:54:57Z","lastAt":"2013-05-28T09:54:57Z","messageCount":1,"participants":["Elliott Cable"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"218637","messageId":"CAPZ477NO6svcG924AE3NijGYusFiUuj=xRnwMxW21FJoC=t28g@mail.gmail.com","threadId":"33956","inReplyTo":null,"subject":"Feature-request: Ordering `git log --graph` based on *author's* timestamp","fromName":"Elliott Cable","fromEmail":"me@ell.io","sentAt":"2013-05-28T09:54:57Z","receivedAt":"2013-05-28T09:54:57Z","isPatch":false,"sender":{"key":"me@ell.io","avatar":"https://gravatar.com/avatar/0d35bb7d7c29b6bbcaafdf13ec70745573d31cb222130cc754a064e707c08d63?d=mp&s=160"},"body":"I use a fairly complex `git-log` command involving `--date-order` to\nget an overview of my repository's status; but unfortunately,\n`--date-order` seems to use the *committer* date, not the *author*\ndate. That means that each time I bring my topic branches up to date\nby rebasing them onto the current upstream, I lose the helpful\nchronological ordering in my `git-log` of relative commits in my topic\nbranches (that is, each branch becomes a single long line, because all\nof its commits got rebased to sequential and nearly-identical\ncommitter timestamps.)\n\nAfter a bit of activity on [a Stack Overflow question][1], I've\nrealized that this is basically impossible without 1. dumping `git\nlog`'s `--graph` feature *entirely*, and writing a very complex custom\nsystem to order and re-graph commits, or 2. getting `git log`\n**itself** patched to support an `--author-order` flag or something.\n\n(I've never posted here before, forgive me if this is the wrong way to\ngo about this … the #git channel on Freenode pointed me here. :)\n\n   [1]: <http://stackoverflow.com/questions/8576503/how-can-i-make-git-log-order-based-on-authors-timestamp>\n"}]}