Opened 10 years ago
Last modified 10 years ago
#11584 closed defect
NoSuchChangeset is raised if repository is empty — at Initial Version
| Reported by: | Jun Omae | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0.2 |
| Component: | version control/browser | Version: | 1.0.1 |
| Severity: | normal | Keywords: | |
| Cc: | Ryan J Ollos | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
In some repository types, browser page raises NoSuchChangeset if empty. Especially, when the repository is default, other registered repositories don't be shown in the browser page by the NoSuchChangeset error.
| Repository type | 1.0.1 | 0.12.5 |
|---|---|---|
| svn | NoSuchChangeset | No error |
| direct-svnfs | No error | No error |
git cached_repository = enabled | NoSuchChangeset | (n/a) |
git cached_repository = disabled | NoSuchChangeset | (n/a) |
| hg | No error | No error |
I think browser page shouldn't raise NoSuchChangeset even if empty.
Note:
See TracTickets
for help on using tickets.
