From: Clayton Whitelaw <cawhitelaw@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
rostedt@goodmis.org
Subject: Re: [PATCH] Documentation/process: Replace broken link with snapshot
Date: Mon, 7 Mar 2022 14:57:21 -0700 [thread overview]
Message-ID: <CADascd-pQarNB6FRuG04Y61ACYxk3nWnw+z5dMV338xUapxvOA@mail.gmail.com> (raw)
In-Reply-To: <20220307134302.faaf3149ead4ccf0fb05a703@linux-foundation.org>
On Mon, Mar 7, 2022 at 2:43 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Mon, 07 Mar 2022 10:48:30 -0700 Jonathan Corbet <corbet@lwn.net> wrote:
>
> > Clayton Whitelaw <cawhitelaw@google.com> writes:
> >
> > > 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
> >
> > We can do that, but first maybe we should ask Andrew (CC'd) whether he
> > has a copy up somewhere that we can link to?
> >
>
> Huh, whatever happened to that?
>
> I had a copy and have restored the file on ozlabs, thanks.
Confirmed I see it's up now.
next prev parent reply other threads:[~2022-03-07 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 17:43 [PATCH] Documentation/process: Replace broken link with snapshot Clayton Whitelaw
2022-03-07 17:48 ` Jonathan Corbet
2022-03-07 21:43 ` Andrew Morton
2022-03-07 21:57 ` Clayton Whitelaw [this message]
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=CADascd-pQarNB6FRuG04Y61ACYxk3nWnw+z5dMV338xUapxvOA@mail.gmail.com \
--to=cawhitelaw@google.com \
--cc=akpm@linux-foundation.org \
--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).