public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rito Rhymes" <rito@ritovision.com>
To: "Jonathan Corbet" <corbet@lwn.net>,
	"Rito Rhymes" <rito@ritovision.com>, <linux-doc@vger.kernel.org>
Cc: "Shuah Khan" <skhan@linuxfoundation.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: set canonical base URL for HTML output
Date: Mon, 23 Mar 2026 15:09:38 -0400	[thread overview]
Message-ID: <DHAED9XZZLVM.2GT0BOHIXJ7MA@ritovision.com> (raw)
In-Reply-To: <87y0ji9zbz.fsf@trenco.lwn.net>

To be clear:

canonical URL + local build = useless

canonical URL set by env var + official published build = source
authority support

hardcoded canonical URL in the source tree + mirror deployments =

1. Benign mirror benefit
    Mirrors inherit a source-authority-supporting default without
    needing to think about it or configure anything themselves.

2. Adversarial / careless mirror mitigation
    Anyone who does not want to preserve that signal must take an
    extra step to remove or override it, adding at least some
    friction to careless or hostile reuse. 

Hardcoding it is simpler, safer and more effective because it makes
preservation of the preferred source the path of least resistance,
requires any departure from it to be explicit, and costs local builds
very little without side effects.

Rito

      reply	other threads:[~2026-03-23 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-21 12:49 [PATCH] docs: set canonical base URL for HTML output Rito Rhymes
2026-03-22 20:40 ` Jonathan Corbet
2026-03-23 18:03   ` Rito Rhymes
2026-03-23 18:26     ` Jonathan Corbet
2026-03-23 19:09       ` Rito Rhymes [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DHAED9XZZLVM.2GT0BOHIXJ7MA@ritovision.com \
    --to=rito@ritovision.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox