Re: log -g --reverse horribly insane

"Shawn O. Pearce" [off-list ref] writes:

OK, I'm just too tired to find this on my own right now.  I'll try
again later after I get some sleep, but maybe someone with a
different sleeping pattern than me will find and fix this before
I arise...

  git log -g --reverse --pretty=oneline

I would have to say that "-g" support was hacked into the normal
revision traversal machinery in such a way to minimize the
amount of changes, without refactoring the two completely
different traversal machineries separate to make the resulting
code maintainable.  Ideal refactoring would require quite a lot
of changes, unfortunately.  I would say it probably would make
sense to make the two options incompatible for now.