From: Randy Dunlap <rdunlap@infradead.org>
To: Linux-Sparse <linux-sparse@vger.kernel.org>,
Christopher Li <sparse@chrisli.org>
Subject: [PATCH] documentation: update email reference link
Date: Thu, 10 Aug 2017 16:11:34 -0700 [thread overview]
Message-ID: <501dfa0c-ab37-74f3-f710-1f885c0bd01c@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
gmane.org was shut down for awhile, then bought by someone else,
and is now being rebuilt. Links to it are not reliable for now,
so add a link to marc.info for the same email message.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
Documentation/sparse.txt | 1 +
1 file changed, 1 insertion(+)
--- sparse-2017-0810.orig/Documentation/sparse.txt
+++ sparse-2017-0810/Documentation/sparse.txt
@@ -43,3 +43,4 @@ Reference:
* Linus' e-mail about __nocast vs __bitwise:
http://article.gmane.org/gmane.linux.kernel.mm/75784
+ http://marc.info/?l=linux-mm&m=133245421127324&w=2
next reply other threads:[~2017-08-10 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 23:11 Randy Dunlap [this message]
2017-08-10 23:34 ` [PATCH] documentation: update email reference link Luc Van Oostenryck
2017-08-10 23:44 ` Randy Dunlap
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=501dfa0c-ab37-74f3-f710-1f885c0bd01c@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).