Diff of a revision range requires a working tree

[Nicholas Allen]

If you perform a diff using a range of revisions Bazaar requires that the branch contains a working tree. This requirement does not make sense as Bazaar does not need any information in the working tree it only needs to check the repository for the changes that were made in that revision range. This happens if you have branches inside a repository that does not have working trees.

For example:

cd repo/project
bzr diff -r X..Y
bzr: ERROR: No WorkingTree exists for /path/to/repo/project

[Nicholas Allen (nick-allen)]

bzr log -r X..Y works as expected. I think anything that you can show the log for you should be able to show the diff for...

[Bubba Siggler (bud3)]

On 2/9/07, John A Meinel <email address hidden> wrote:
>
> *** This bug is a duplicate of bug 6700 ***
>
> ** This bug has been marked a duplicate of bug 6700
> bzr diff -r 10..20 http://foo" unsupported

        John Meinel
          I ran *bzr missing under bughelper'.. What I got was missing 10
revision(s): Do I run *bzr update`

          Bubba

--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFkcN7yXWcajQQndYRAgbqAKCMyXN9Jx4g0X7jocg+aUSFz0x4LwCgrURW
eGtqLjpzQVYa9+gzpCRtB84=
=zrpM
-----END PGP SIGNATURE-----