[Bug 215903] Re: 'bzr pull' should report number of new revisions retrieved

[Matthew D. Fuller]

On Sun, Apr 20, 2008 at 02:37:28AM -0000 I heard the voice of
Aaron Bentley, and lo! it spake thus:
> fullermd wrote:
> 
> > (pull -v != log)
> 
> That seems a rather terse rationale for not using the functionality
> that was intended to address this use case.

Because it wasn't rationale, it was a quick attempt to forestall a
discussion of no relevance to the bug.

log is log.  Other commands may simulate small portions of log, but
they do it badly and ad-hoc'ly.  How do you use --forward or --short
or --line with pull -v?  Heck, how do you make pull do a 'log -v' to
show the files in each rev (pull -vv?)?  --show-ids?

It happens with other commands too; how do you do --forward with
missing?  That at least you CAN do, but it's called -reverse, because
reverse is just like forward, right?

In my particular case, I use my `bzr flog` alias, which log's
--forward --short.  pull can't do that at all.  But until pull -v can
do everything log can do (and ideally via the same mechanisms, so that
when log grows more it doesn't have to be manually reduplicated
another half dozen places in the code) it will never == log.


-- 
Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.