svn commit: r1923953 - /subversion/trunk/subversion/tests/README
| Newsgroups | gmane.comp.version-control.subversion.svn |
|---|---|
| Message-ID | <[email protected]> |
Author: dsahlberg
Date: Fri Feb 21 07:47:59 2025
New Revision: 1923953
URL: http://svn.apache.org/viewvc?rev=1923953&view=rev
Log:
Replace tigris.org url with apache.org.
* subversion/tests/README
Replace link to issue tracker
Modified:
subversion/trunk/subversion/tests/README
Modified: subversion/trunk/subversion/tests/README
URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/tests/README?rev=1923953&r1=1923952&r2=1923953&view=diff
==============================================================================
--- subversion/trunk/subversion/tests/README (original)
+++ subversion/trunk/subversion/tests/README Fri Feb 21 07:47:59 2025
@@ -137,7 +137,7 @@ By definition, if you write a new test w
assumed that the test is for a known bug. In these cases it is
recommended that you associate an issue in the issue tracker with the
XFailing test. This ensures that the issue tracker is the authoritative
-list of known bugs -- see http://subversion.tigris.org/issue-tracker.html.
+list of known bugs -- see https://subversion.apache.org/issue-tracker.html.
You may need to create a new issue if one doesn't already exist.
For C tests simply add a comment noting any associated issue: