id summary reporter owner description type status priority milestone component version severity resolution keywords cc branch changelog apichanges internalchanges 11584 NoSuchChangeset is raised if repository is empty Jun Omae Jun Omae "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." defect closed normal 1.0.2 version control/browser 1.0.1 normal fixed Ryan J Ollos " - Prevent `NoSuchChangeset` error on browser view if default repository is empty. - Prevent `NoSuchChangeset` error from `GitNode.__init__` if git repository is empty."