#987 closed defect (fixed)
"Viev rev:" value reused when not expected - quite confusing
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | normal | Milestone: | 0.10 |
Component: | version control/browser | Version: | 0.8 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
We have done a test-conversion of an existing repository into SVN using cvs2svn.
While browsing the result with Trac, I observed that some files in trunk were not the newest! They were shown correctly in the corresponding tags path.
After some clicking "Back" and "Next" in IE, I found out that the entry field "View rev:" (top right, normally updated automatically) was at "10108". Clearing the field and reloading the page gave the correct output.
A lot of "Back" clicking revealed, that it had been "sticky" at that value since I clicked that number (with a "View revision log" pop up) in a file listing. After that I probably used the "Back" button.
After that all subsequent Trac operations were relative to that revision! Dunno what was intended, but this is confusing.
Attachments (0)
Change History (4)
comment:1 by , 20 years ago
comment:3 by , 19 years ago
Milestone: | → 0.10 |
---|---|
Owner: | changed from | to
In the TracBrowser, if the revision is not specified, the current revision number corresponding to the head will be used instead. The problem here is that once the revision is set, it remains sticky, as you said.
One way to be sure to stay on the head is to explicitely specify "head" for the viewed revision, in this View revision: field.
The Browse Source link should probably do this, in a VersioningSystemBackend independent way, though.
Just cross checked with your installation, running 0.8. The user interface has been changed, "Viev rev:" selection no longer there, so maybe the problem is not relevant after 0.8?