Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-492

Audit use of error codes

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • all
    • Beta
    • src
    • None

    Description

      The meaning and usage of the defined error codes is not documented, and some
of the error codes seem to be duplicates. This leads to confusing error reports
(see, e.g., issue #491).

To do:
- Document the meaning of each error code (probably means checking
  every use).
- Weed out codes with similar meanings
- Add *new* codes where current codes are overloaded

      Attachments

        Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. SVN-434 NEEDED: Public API with useful error messages.

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SVN-491 'svn status' needs better error reporting

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SVN-447 need clearer error message in out-of-date case

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SVN-474 uninformative error if bad auth info on commit

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              brane Branko Čibej
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: