mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Zefan Li <lizefan@huawei.com>, Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Cgroups <cgroups@vger.kernel.org>,
	Steve Wahl <steve.wahl@hpe.com>
Subject: Re: [PATCH] cpuset: Remove stale URLs in the MAINTAINERS entry
Date: Sun, 27 Dec 2020 22:01:35 -0800	[thread overview]
Message-ID: <2822d565280536f36ea6ddd521a7716813ef85a2.camel@perches.com> (raw)
In-Reply-To: <42668f2c-5ea1-da38-918e-ac4c86e3f03d@huawei.com>

On Mon, 2020-12-28 at 11:17 +0800, Zefan Li wrote:
> Those URLs are no longer accessable.
> 
> Reported-by: Steve Wahl <steve.wahl@hpe.com>
> Signed-off-by: Zefan Li <lizefan@huawei.com>
> ---
>  MAINTAINERS | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ae9b1dd748c4..2fe8eb54639e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4477,8 +4477,6 @@ CONTROL GROUP - CPUSET
>  M:	Li Zefan <lizefan@huawei.com>
>  L:	cgroups@vger.kernel.org
>  S:	Maintained
> -W:	http://www.bullopensource.org/cpuset/
> -W:	http://oss.sgi.com/projects/cpusets/

The general argument to avoid removal of these no longer valid links
is that they may still be available from archive.org.

For instance:

https://web.archive.org/web/20170512010721/http://oss.sgi.com/projects/cpusets/

It may be appropriate to copy the content into a local Documentation
file somewhere to avoid the need to lookup old reference links.



  reply	other threads:[~2020-12-28  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28  3:17 Zefan Li
2020-12-28  6:01 ` Joe Perches [this message]
2020-12-28  6:31   ` Zefan Li
2021-01-04 15:28     ` Steve Wahl

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=2822d565280536f36ea6ddd521a7716813ef85a2.camel@perches.com \
    --to=joe@perches.com \
    --cc=cgroups@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=steve.wahl@hpe.com \
    --cc=tj@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

all inboxes | Powered by JetHome®