git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: log -g --reverse horribly insane

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 19, 2007, 09:09 UTC
Message-ID
<7v8x87dh5r.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20070819085624.GU27913@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
Show 6 quoted lines
> 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.

Previous: Shawn O. Pearce
Message 2 of 2 in “log -g --reverse horribly insane”
  1. Shawn O. PearceAug 19, 2007
  2. Junio C HamanoAug 19, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.