From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ramunas Geciauskas <kernel@geciauskas.com>,
corbet@lwn.net, linux-doc@vger.kernel.org
Cc: Ramunas Geciauskas <kernel@geciauskas.com>
Subject: Re: [PATCH] Documentation/admin-guide: update URL of LKML information link
Date: Mon, 31 Dec 2018 10:31:56 +0200 [thread overview]
Message-ID: <87a7kmumf7.fsf@intel.com> (raw)
In-Reply-To: <20181229210000.1132-1-kernel@geciauskas.com>
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.
BR,
Jani.
>
> Signed-off-by: Ramunas Geciauskas <kernel@geciauskas.com>
> ---
> Documentation/admin-guide/reporting-bugs.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/reporting-bugs.rst b/Documentation/admin-guide/reporting-bugs.rst
> index 4650edb8840a..49ac8dc3594d 100644
> --- a/Documentation/admin-guide/reporting-bugs.rst
> +++ b/Documentation/admin-guide/reporting-bugs.rst
> @@ -67,7 +67,7 @@ If you can't figure out which subsystem caused the issue, you should file
> a bug in kernel.org bugzilla and send email to
> linux-kernel@vger.kernel.org, referencing the bugzilla URL. (For more
> information on the linux-kernel mailing list see
> -http://www.tux.org/lkml/).
> +http://vger.kernel.org/lkml/).
>
>
> Tips for reporting bugs
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2018-12-31 8:32 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 [this message]
2018-12-31 15:03 ` Ramunas Geciauskas
2019-01-03 16:23 ` Jonathan Corbet
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=87a7kmumf7.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.