user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: meta@public-inbox.org,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: generic message-id redirector
Date: Mon, 1 Feb 2021 17:17:03 +0000	[thread overview]
Message-ID: <20210201171703.GA25295@dcvr> (raw)
In-Reply-To: <20210201132630.y53ydk4w6o7fyrzp@pengutronix.de>

Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> On Mon, Feb 01, 2021 at 11:10:49AM +0000, Eric Wong wrote:
> > To get /r/, you can use the "mount" directive in the
> > Plack::Builder DSL as shown in example/newswww.psgi
> 
> > > Is there some additional code or configuration necessary to make this
> > > work? Am I missing something?
> > 
> > That said, I seem to recall lore.kernel.org/r/ existing before NewsWWW,
> > so maybe it was something else, too.  (It may have even existed
> > somewhere on kernel.org before lore)
> 
> @Konstantin: It would be great if you shared how this is implemented on
> lore.kernel.org. For me this redirection is so convenient I definitely
> want to have it. I wonder if it is considered good by others, too. Then
> maybe implement it in the core?!

Fwiw, I'm pretty sure NewsWWW can do everything /r/ does (and
/r/ may use NewsWWW under-the-hood.  It might just be inertia
if /r/ is some other implementation, or if it can redirect to
3rd-party (non-public-inbox) URLs.

  reply	other threads:[~2021-02-01 17:17 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 [this message]
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

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=20210201171703.GA25295@dcvr \
    --to=e@80x24.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=meta@public-inbox.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).