From: Jonathan Corbet <corbet@lwn.net>
To: Ramunas Geciauskas <kernel@geciauskas.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation/admin-guide: update URL of LKML information link
Date: Thu, 3 Jan 2019 09:23:46 -0700 [thread overview]
Message-ID: <20190103092346.0c900e7c@lwn.net> (raw)
In-Reply-To: <20181231100309.07b871f1@triton.namas.geciauskas.com>
On Mon, 31 Dec 2018 10:03:09 -0500
Ramunas Geciauskas <kernel@geciauskas.com> wrote:
> On Mon, 31 Dec 2018 10:31:56 +0200
> Jani Nikula <jani.nikula@linux.intel.com> wrote:
>
> > On Sat, 29 Dec 2018, Ramunas Geciauskas <kernel@geciauskas.com> wrote:
> > > Information regarding linux-kernel mailing list is no longer hosted on tux.org
> > > Update the link to point to the one available at kernel.org
> >
> > Arguably there's no useful current information wrt reporting bugs at the
> > updated URL either.
>
> A lot of information in there is rather outdated indeed,
> however it does contain explanation how to subscribe/unsubscribe
> to LKML (or rather "why you shouldn't").
>
> Would you prefer to get rid of the link completely?
> The current one is dead since late 2016 (so it doesn't seem it will come back)
I'll go ahead and apply the patch for now; an old link is better than a
dead one, methinks. All of this documentation needs a deeper cleaning and
redo, of course...
Thanks,
jon
prev parent reply other threads:[~2019-01-03 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 21:00 [PATCH] Documentation/admin-guide: update URL of LKML information link Ramunas Geciauskas
2018-12-31 8:31 ` Jani Nikula
2018-12-31 15:03 ` Ramunas Geciauskas
2019-01-03 16:23 ` Jonathan Corbet [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=20190103092346.0c900e7c@lwn.net \
--to=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=kernel@geciauskas.com \
--cc=linux-doc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).