Re: Switching to bzr: what remains to be done?

[Dan Nicolaescu <dann@ics.uci.edu>]

Karl Fogel <karl.fogel@canonical.com> writes:

  > Progress report on the 4 bugs we've highlighted as blockers:
  > 
  >    1) 'bzr log' only takes a single file argument
  >        (https://bugs.launchpad.net/bzr/+bug/211852)
  > 
  >        Developer vila has commented in the bug, but there is no
  >        timeline to fix it.  I'm asking vila whether he plans to.
  > 
  >    2) 'bzr log SUBDIR' doesn't show all changes under SUBDIR
  >        (https://bugs.edge.launchpad.net/bzr/+bug/97715)
  > 
  >        Developer abentley has commented that this is hard (at least,
  >        that's how I interpret "This isn't really practical without
  >        changes to the inventory format.")  Is this one definitely a
  >        blocker for us, or just a nice-to-have?

Some parts of emacs are maintained in a different place, (Gnus and org
come to mind, but probably there's more).  Not being able to do a bzr log on
a subdir might be a big problem for those projects (or for Miles that
handles merging).  You might want to ask them directly.

Now _IMHO_, a VCS that cannot do a log operation on a subdirectory is a
non-starter for anything that has subdirectories.