Modify ↓
Opened 20 years ago
Closed 20 years ago
#1095 closed defect (fixed)
Entering non-existing revision number fails
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | version control/browser | Version: | 0.8 |
Severity: | minor | Keywords: | |
Cc: | manuzhai@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
In a repository that has 100 revisions, entering 101 in the browser will cause a failure. I would expect it to either tell me the revision doesn't exist or simply go to the latest revision.
Attachments (0)
Change History (3)
comment:1 by , 20 years ago
Cc: | added |
---|
comment:2 by , 20 years ago
comment:3 by , 20 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
It's been fixed since 0.8 to show the invalid rev. number message.
Note:
See TracTickets
for help on using tickets.
You should get the message:
…which is pretty close. Are you suggesting we change the error message to something like
?