From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-i3c@lists.infradead.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Kuan-Wei Chiu <visitorckw@gmail.com>,
linus@ucla.edu
Subject: Re: [PATCH] bitops: use safer link explaining the algorithm
Date: Mon, 27 Jan 2025 12:09:37 +0100 [thread overview]
Message-ID: <Z5dpcZdHrn6XVlCI@ninjato> (raw)
In-Reply-To: <CAMuHMdWmE2UiE7kwAyQKONSE_ytrNux+Wwu-v__K=jjpAutxqw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]
> Is the plan to replace all weblinks by webarchive links as a precaution?
Dunno if there is a plan but 'git grep' showed at least a trend.
> Even websites backed by big companies may disappear[1]...
I think you are comparing apples with oranges here. The main site
(intel.com) still exists last time I checked.
> Putting the webarchive link here also impacts the funloop.org server
> statistics, downplaying its relevance, and possibly even causing an
> earlier shutdown.
Could be. But could also be the opposite: not using an alternative will
eat all the traffic and increase maintenance duty, so it will be shut
down because of too much work. Who has the better crystal ball?
> The URL can always be updated when the original site disappears.
Still, the good thing is that the site is *now* backed by the Wayback
Machine. I needed to request the backup because I wanted the link.
That all being said, I don't care much which link we use. I just wanted
to address review comments.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 111 bytes --]
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2025-01-29 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 13:01 [PATCH] bitops: use safer link explaining the algorithm Wolfram Sang
2025-01-25 15:10 ` Geert Uytterhoeven
2025-01-26 17:46 ` Yury Norov
2025-01-26 20:16 ` Rasmus Villemoes
2025-01-27 11:30 ` Wolfram Sang
2025-01-27 11:28 ` Wolfram Sang
2025-01-28 13:10 ` Linus Arver
2025-01-27 11:09 ` Wolfram Sang [this message]
2025-01-27 13:32 ` Geert Uytterhoeven
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=Z5dpcZdHrn6XVlCI@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=alexandre.belloni@bootlin.com \
--cc=geert@linux-m68k.org \
--cc=linus@ucla.edu \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=visitorckw@gmail.com \
--cc=yury.norov@gmail.com \
/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