linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clayton Whitelaw <cawhitelaw@google.com>
To: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
	rostedt@goodmis.org, Clayton Whitelaw <cawhitelaw@google.com>
Subject: [PATCH] Documentation/process: Replace broken link with snapshot
Date: Mon,  7 Mar 2022 10:43:01 -0700	[thread overview]
Message-ID: <20220307174301.1852106-1-cawhitelaw@google.com> (raw)

The link is for the reference article, "The perfect patch":
https://www.ozlabs.org/~akpm/stuff/tpp.txt

This link is down currently and apparently since at least 2022 Jan:
https://web.archive.org/web/20220112192643/https://www.ozlabs.org/~akpm/stuff/tpp.txt

Replace with most recent good snapshot, from 2021 Oct

Signed-off-by: Clayton Whitelaw <cawhitelaw@google.com>
---
 Documentation/process/submitting-patches.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index 31ea120ce..2a4c4065d 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -802,7 +802,7 @@ References
 ----------
 
 Andrew Morton, "The perfect patch" (tpp).
-  <https://www.ozlabs.org/~akpm/stuff/tpp.txt>
+  <https://web.archive.org/web/20211008233254/https://www.ozlabs.org/~akpm/stuff/tpp.txt>
 
 Jeff Garzik, "Linux kernel patch submission format".
   <https://web.archive.org/web/20180829112450/http://linux.yyz.us/patch-format.html>
-- 
2.35.1.616.g0bdcbb4464-goog


             reply	other threads:[~2022-03-07 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 17:43 Clayton Whitelaw [this message]
2022-03-07 17:48 ` [PATCH] Documentation/process: Replace broken link with snapshot Jonathan Corbet
2022-03-07 21:43   ` Andrew Morton
2022-03-07 21:57     ` Clayton Whitelaw
2022-03-07 18:40 ` Matthew Wilcox

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=20220307174301.1852106-1-cawhitelaw@google.com \
    --to=cawhitelaw@google.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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).