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. ;)
martin
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. ;)
martin
Re: [RFC] cg-log -r order:matters
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.