[BUG] Diff on revision range for branch in repository without working trees is not possible

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nicholas Allen wrote:
> 
>> At present, diffs can only be performed in working trees, so this is
>> more of a known limitation than an actual bug.
> 
> But then you can't examine any of the diffs on the server as the server
> will not have working tree as it does not need one. Isn't that a major
> limitation? When I specify a revision range there is no need for the
> working copy so isn't this really a bug anyway? If I just specify one
> revision then it needs to compare the working tree to the revision
> specified but for a range all info is held in the repository so I don't
> think this should be necessary and to me at least it is a bug...

It is not a necessary limitation, but it is not a bug, either.

You are welcome to rewrite the command.  Bear in mind, it should support
the following syntaxes:

# Compare two files in the same tree
$ bzr diff file1 file2

# Compare two files in the basis tree
$ bzr diff file1 file2 -r -1

# Compare two files in different trees
$ bzr diff tree1/file1 tree2/file2

# Compare the same file in different trees
$ bzr diff file1 tree2

# Compare two trees
$ bzr diff tree1 tree2

# Compare tree1 r2 with tree2 r2
$ bzr diff -r1..2 tree1 tree2

# Compare tree1 r1 with tree1 r2
$ bzr diff -r1..2 tree1

# Compare the basis trees of two branches
$ bzr diff branch1 branch2

# Compare branch1 r1 with branch2 r2
$ bzr diff branch1 -r 1..2 branch2

# Compare files in branch1 and branch2 basis
$ bzr diff branch1/file1 branch2/file2

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFFzLB90F+nu1YWqI0RAkaEAJ0YJ3R8c3ParWS0WdmkEOQ5msdlQgCeOe7q
vKHhT4AbkkawJkXdb/HfJKw=
=UJ/E
-----END PGP SIGNATURE-----