Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Mar 2021 19:59:36 GMT
From:      Rene Ladan <rene@FreeBSD.org>
To:        doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org
Subject:   git: acc10bbdad - main - problem-reports: convert a svnweb link for UPDATING to cgit.
Message-ID:  <202103291959.12TJxaL1068779@gitrepo.freebsd.org>

next in thread | raw e-mail | index | archive | help
The branch main has been updated by rene:

URL: https://cgit.FreeBSD.org/doc/commit/?id=acc10bbdadf2a9ce68e68d92a7583dade59d4822

commit acc10bbdadf2a9ce68e68d92a7583dade59d4822
Author:     Rene Ladan <rene@FreeBSD.org>
AuthorDate: 2021-03-29 19:47:58 +0000
Commit:     Rene Ladan <rene@FreeBSD.org>
CommitDate: 2021-03-29 19:47:58 +0000

    problem-reports: convert a svnweb link for UPDATING to cgit.
    
    # Uncomment and complete these metadata fields, as appropriate:
    #
    # PR:
    # Submitted by:
    # Reported by:
    # Reviewed by:
    # Approved by:
    # Obtained from:
    # MFC after:
    # MFH:
    # Relnotes:
    # Security:
    # Sponsored by:
    # Pull Request:
    # Differential Revision:
    #
    # Description of fields to fill in above:                 72 columns --|
    # PR:                       If and which Problem Report is related.
    # Submitted by:             If someone else sent in the change.
    # Reported by:              If someone else reported the issue.
    # Reviewed by:              If someone else reviewed your modification.
    # Approved by:              If you needed approval for this commit.
    # Obtained from:            If the change is from a third party.
    # MFC after:                N [day[s]|week[s]|month[s]].  Request a reminder email.
    # MFH:                      Ports tree branch name.  Request approval for merge.
    # Relnotes:                 Set to 'yes' for mention in release notes.
    # Security:                 Vulnerability reference (one per line) or description.
    # Sponsored by:             If the change was sponsored by an organization.
    # Pull Request:             https://github.com/freebsd/<repo>/pull/### (*full* GitHub URL needed).
    # Differential Revision:    https://reviews.freebsd.org/D### (*full* phabric URL needed).
---
 documentation/content/en/articles/problem-reports/_index.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/content/en/articles/problem-reports/_index.adoc b/documentation/content/en/articles/problem-reports/_index.adoc
index 5733c0ae46..86dbb2d877 100644
--- a/documentation/content/en/articles/problem-reports/_index.adoc
+++ b/documentation/content/en/articles/problem-reports/_index.adoc
@@ -96,7 +96,7 @@ For FreeBSD, this means:
 * Next, the searchable https://bugs.freebsd.org/bugzilla/query.cgi[FreeBSD PR database] (Bugzilla). Unless the problem is recent or obscure, there is a fair chance it has already been reported.
 * Most importantly, attempt to see if existing documentation in the source base addresses your problem.
 + 
-For the base FreeBSD code, you should carefully study the contents of [.filename]#/usr/src/UPDATING# on your system or the latest version at https://svnweb.freebsd.org/base/head/UPDATING?view=log[https://svnweb.freebsd.org/base/head/UPDATING?view=log].
+For the base FreeBSD code, you should carefully study the contents of [.filename]#/usr/src/UPDATING# on your system or the latest version at https://cgit.freebsd.org/src/tree/UPDATING[https://cgit.freebsd.org/src/tree/UPDATING].
 (This is vital information if you are upgrading from one version to another-especially if you are upgrading to the FreeBSD-CURRENT branch).
 + 
 However, if the problem is in something that was installed as a part of the FreeBSD Ports Collection, you should refer to [.filename]#/usr/ports/UPDATING# (for individual ports) or [.filename]#/usr/ports/CHANGES# (for changes that affect the entire Ports Collection).



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202103291959.12TJxaL1068779>