{"thread":{"id":"9573","subject":"log -g --reverse horribly insane","startedAt":"2007-08-19T08:56:24Z","lastAt":"2007-08-19T09:09:52Z","messageCount":2,"participants":["Shawn O. Pearce","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"50996","messageId":"20070819085624.GU27913@spearce.org","threadId":"9573","inReplyTo":null,"subject":"log -g --reverse horribly insane","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-08-19T08:56:24Z","receivedAt":"2007-08-19T08:56:24Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"OK, I'm just too tired to find this on my own right now.  I'll try\nagain later after I get some sleep, but maybe someone with a\ndifferent sleeping pattern than me will find and fix this before\nI arise...\n\n  git log -g --reverse --pretty=oneline\n\nDoes not produce anything useful.  Results are ranging from getting\na single line with upwards of 50 commits on it and a corrupt log\nmessage to lines with no log message and only one commit, even\nthough the non --reverse output has over 200 results to report.\n\n  git log -g --reverse\n\nDoes not show the reflog message headers, but is otherwise fine.\nSo it shows the history according to the reflog (I think that's\nwhat I saw) but isn't showing the data I asked for with -g.\n\nResults are the same for HEAD's reflog as for any other branch in\nmy tree.  Basically its nutso.  I think we need to either support\n-g --reverse combination properly, or we need to disallow it.\nThe current behavior is uh, not user friendly.\n\n-- \nShawn.\n"},{"id":"50997","messageId":"7v8x87dh5r.fsf@gitster.siamese.dyndns.org","threadId":"9573","inReplyTo":"20070819085624.GU27913@spearce.org","subject":"Re: log -g --reverse horribly insane","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-08-19T09:09:52Z","receivedAt":"2007-08-19T09:09:52Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Shawn O. Pearce\" <spearce@spearce.org> writes:\n\n> OK, I'm just too tired to find this on my own right now.  I'll try\n> again later after I get some sleep, but maybe someone with a\n> different sleeping pattern than me will find and fix this before\n> I arise...\n>\n>   git log -g --reverse --pretty=oneline\n\nI would have to say that \"-g\" support was hacked into the normal\nrevision traversal machinery in such a way to minimize the\namount of changes, without refactoring the two completely\ndifferent traversal machineries separate to make the resulting\ncode maintainable.  Ideal refactoring would require quite a lot\nof changes, unfortunately.  I would say it probably would make\nsense to make the two options incompatible for now.\n"}]}