Issue 635: post-review cannot deal with files not in current version of
repository, when using --revision-range
Comment #1 by jsankey:
I have seen a similar problem running the latest post-review on Windows.
In my case
I had renamed files in the change, and the intial problem was triggered by
handle_renames. I hacked the script to get past this point and hit the
in convert_to_absolute_paths. In both cases post-review was trying to run
on files no longer in my working copy.
More generally speaking, if the revision range specified is in the past,
info on local working copy files is not going to work. These working files
longer exist, or the info may be affected by subsequent changes that do not
the revision range.
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
You received this message because you are subscribed to the Google Groups
To post to this group, send email to email@example.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at