From: Jonathan Corbet <corbet@lwn.net>
To: Jacob Huisman <jacobhuisman@kernelthusiast.com>
Cc: Federico Vaga <federico.vaga@vaga.pv.it>,
Harry Wei <harryxiyou@gmail.com>,
Alex Shi <alex.shi@linux.alibaba.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: process: fix broken link
Date: Sat, 24 Aug 2019 15:18:08 -0600 [thread overview]
Message-ID: <20190824151808.782b77c4@lwn.net> (raw)
In-Reply-To: <20190816122209.5bz4rlln5cahn7ki@jacob-MS-7A62>
On Fri, 16 Aug 2019 13:22:09 +0100
Jacob Huisman <jacobhuisman@kernelthusiast.com> wrote:
> http://linux.yyz.us/patch-format.html seems to be down since
> approximately September 2018. There is a working archive copy on
> arhive.org. Replaced the links in documenation + translations.
>
> Signed-off-by: Jacob Huisman <jacobhuisman@kernelthusiast.com>
> ---
> Documentation/process/howto.rst | 2 +-
> Documentation/process/submitting-patches.rst | 2 +-
> Documentation/translations/it_IT/process/howto.rst | 2 +-
> Documentation/translations/it_IT/process/submitting-patches.rst | 2 +-
> Documentation/translations/ja_JP/SubmittingPatches | 2 +-
> Documentation/translations/ja_JP/howto.rst | 2 +-
> Documentation/translations/ko_KR/howto.rst | 2 +-
> Documentation/translations/zh_CN/process/howto.rst | 2 +-
> Documentation/translations/zh_CN/process/submitting-patches.rst | 2 +-
> 9 files changed, 9 insertions(+), 9 deletions(-)
Dead links don't help anybody, so I've applied this. I have to wonder,
though, whether there is really value in carrying around a link to a page
that hasn't been maintained in years. Almost everything that appears
there is already in submitting-patches.rst; maybe we could see if there's
anything that's missing, add it, then drop the link?
Thanks,
jon
prev parent reply other threads:[~2019-08-24 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 12:22 [PATCH] docs: process: fix broken link Jacob Huisman
2019-08-19 5:50 ` Federico Vaga
2019-08-24 21:18 ` 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=20190824151808.782b77c4@lwn.net \
--to=corbet@lwn.net \
--cc=alex.shi@linux.alibaba.com \
--cc=federico.vaga@vaga.pv.it \
--cc=harryxiyou@gmail.com \
--cc=jacobhuisman@kernelthusiast.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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).