[all-commits] [llvm/llvm-project] 2d6d05: [libc++][docs] Use project-local links in release ...

Reid Kleckner via All-commits all-commits at lists.llvm.org
Fri Oct 2 17:03:25 PDT 2026


  Branch: refs/heads/users/rnk/fix-self-doclink-libcxx
  Home:   https://github.com/llvm/llvm-project
  Commit: 2d6d050930b1358216d01612e159c5dc05890b9c
      https://github.com/llvm/llvm-project/commit/2d6d050930b1358216d01612e159c5dc05890b9c
  Author: Reid Kleckner <rkleckner at nvidia.com>
  Date:   2026-10-02 (Fri, 02 Oct 2026)

  Changed paths:
    M libcxx/docs/Helpers/ReleaseNotesTemplate.rst
    M libcxx/docs/ReleaseNotes/20.rst
    M libcxx/docs/ReleaseNotes/21.rst
    M libcxx/docs/ReleaseNotes/22.rst
    M libcxx/docs/ReleaseNotes/23.rst
    M libcxx/docs/ReleaseNotes/24.rst

  Log Message:
  -----------
  [libc++][docs] Use project-local links in release notes

Replace absolute libc++ homepage links with Sphinx document references in
release notes 20 through 24 and the release-note template.

I would leave these historical documents alone, but I have to fix these,
or the doc build will fail with warnings when I enable the absolute
self-link Sphinx doc build warning.

Validation: docs-libcxx-html, followed by a fresh Sphinx rebuild (-E), on
a merge of the three independent self-link fixes with the checker enabled
and warnings-as-errors disabled. No self-link warnings or new warning
messages compared with the audit baseline.

Part of #214861

Assisted-by: Codex



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications


More information about the All-commits mailing list