changeset?old=0&new=n&... should set old to (n-1)

[olegov@…]

when viewing a changeset, svn uses old=0 to represent "previous revision", but in trac old is set to n if old == 0.

this change would help integration with a fogbugz bugtracker

[olegov@…]

actually, as far as fogbugz integration, this doesn't matter so much, because all is well if i don't specify the rev, i.e.: changeset?old_path=…&new_path=…&new=n performs the correct operation. nevertheless, defaulting old to n is not useful.

[Christian Boos]

Well, the idea is that when old == new == n, it's like saying that you want to look at changeset n only, i.e. the changes introduced in revision n.

If you don't want to look at the differences between two arbitrary paths but rather at the changes that were introduced in revision n below a given path, you simply need restricted changesets URLs: /changeset/n/some/path.

old_path and new_path should be used only when you need to compare e.g. different branches…