'bzr diff -rnn..nn some_file 'will return nothing if some_file was in a different directory back in nn..nn

[James Troup]

$ bzr diff -r3029..3055 sync-source.py
$ bzr diff -r3029..3055 ../sync-source.py
=== modified file 'a/scripts/sync-source.py'
[ ... ]

This is similar to #3619, but the bug here/difference IMO, is that 'bzr diff' when given specific revisions, should be able to figure out the file location at that time without user help.

[Aaron Bentley (abentley)]

I can't reproduce this: in bzr.dev:

bzr diff -r -500 bzrlib/tests/test_diff.py and bzr diff -r -500 bzrlib/selftest/testdiff.py produce the same results.

[Aaron Bentley (abentley)]

Oh, I get it. The bug is that bzr diff -r -500..501 bzrlib/tests/test_diff.py doesn't work.

In other words, diff should consider the file ids of the working tree, as well as those in the historical trees, when mapping filenames to file ids.

[John A Meinel (jameinel)]

I believe this fix was merged in:
1843 Canonical.com Patch Queue Manager 2006-07-06
      diff always permits filenames from working directory

So I'm marking it as released. Re-open if this is incorrect.