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

Re: [RFC] cg-log -r order:matters

From
Petr Baudis <pasky@suse.cz>
Date
Sep 21, 2005, 13:46 UTC
Message-ID
<20050921134638.GA17981@pasky.or.cz>
In-Reply-To
<46a038f905082304126e8ecd65@mail.gmail.com>

Dear diary, on Tue, Aug 23, 2005 at 01:12:58PM CEST, I got a letter where Martin Langhoff <martin.langhoff@gmail.com> told me that...

> It's sometimes unclear which head is "ahead" of the other. If I get
> the order wrong, cg-log shows no log output. Is this expected?
> 
> I was expecting a warning, or a reverse-ordered log. Or both. ;)

The thing is, how cg-log -r from:to is implemented is really "show me all the ancestors of $to excepts ancestors of $from". So if $to is an ancestor of $from, it will logically show nothing. But checking that condition separately would take _very_ long time. And just producing a warning when log output would be empty, that seems too noisy to me.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
Previous: Martin Langhoff
Message 2 of 2 in “[RFC] cg-log -r order:matters”
  1. Martin LanghoffAug 23, 2005
  2. Petr BaudisSep 21, 2005

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.