goals for 0.10 development

[Martin Pool]

On  3 Aug 2006, Martin Pool <mbp at canonical.com> wrote:
> On  3 Aug 2006, Michael Ellerman <michael at ellerman.id.au> wrote:
> > On 8/2/06, Martin Pool <mbp at canonical.com> wrote:
> > >  - bzr log per file to show more relevant data, and be faster. (needs
> > > speccing from ui aspect, mbp to do so, then ???)
> > 
> > Personally I think this is an adoption blocker. On large trees it's
> > very useful to be able to say "show the log entries that touch this
> > file/directory tree". Performance would be nice, but the functionality
> > is key IMHO.
> 
> It works, it just is not well defined.  Specifically (iirc) 'bzr log
> FILE' tells you about all mainline revisions which touched the file, and
> *all* the merges into them, even the ones which did not touch it.  On a
> busy tree this means that most of the logs printed are irrelevant, which
> is not very helpful[*].
> 
> I would much rather see all the merges which brought that file in, but
> only the merged-in revisions that affected it.

There's a bug

  "bzr log <file> displays irrelevant log records"
  https://launchpad.net/products/bzr/+bug/51980
-- 
Martin