From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Eric Wong <e@80x24.org>, meta@public-inbox.org
Subject: Re: generic message-id redirector
Date: Tue, 2 Feb 2021 15:02:51 +0100 [thread overview]
Message-ID: <20210202140251.lroxjgrmx34t3eqw@pengutronix.de> (raw)
In-Reply-To: <20210202130639.sfhqdfrvldemetou@nitro.local>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Hello,
On Tue, Feb 02, 2021 at 08:06:39AM -0500, Konstantin Ryabitsev wrote:
> On Tue, Feb 02, 2021 at 09:08:10AM +0100, Uwe Kleine-König wrote:
> > (It seems from the outside I have to use /r/ though for lore.kernel.org,
> > https://lore.kernel.org/20201215212228.185517-2-clemens.gruber@pqgruber.com
> > at least doesn't work.)
>
> That's just a side-effect of our setup -- we define a reverse proxy
> lookup for every known list and the toplevel itself isn't mounted. The
> reason we use /r/ is because lkml.kernel.org/r/msgid was an existing
> redirector service we ran for 10+ years (that used to redirect to an
> external service before lore.kernel.org).
>
> There's no reason for anyone else to mimic /r/ the way we are doing it.
Ack, I wonder if for interoperability it would make sense to allow URLs
without /r/ on lore.kernel.org and maybe then even change b4 to not use
it?!
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-02-02 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 10:41 generic message-id redirector Uwe Kleine-König
2021-02-01 11:10 ` Eric Wong
2021-02-01 13:26 ` Uwe Kleine-König
2021-02-01 17:17 ` Eric Wong
2021-02-01 19:22 ` Konstantin Ryabitsev
2021-02-02 8:08 ` Uwe Kleine-König
2021-02-02 13:06 ` Konstantin Ryabitsev
2021-02-02 14:02 ` Uwe Kleine-König [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210202140251.lroxjgrmx34t3eqw@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=e@80x24.org \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).