From: Finn Thain <fthain@telegraphics.com.au>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Matt Turner <mattst88@gmail.com>,
trivial@kernel.org, linux-kernel@vger.kernel.org,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Dimitry Torokhov <dmitry.torokhov@gmail.com>,
Ben Pfaff <blp@cs.stanford.edu>,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH]Update-broken-web-addresses-in-the-kernel
Date: Wed, 22 Sep 2010 12:41:25 +1000 (EST) [thread overview]
Message-ID: <alpine.LNX.2.00.1009221205330.4570@nippy.intranet> (raw)
In-Reply-To: <4C98D8AA.80606@gmail.com>
On Tue, 21 Sep 2010, Justin P. Mattock wrote:
> On 09/20/2010 10:17 PM, Finn Thain wrote:
> >
> > I would say that if a URL is in the web archive, then no patch is needed.
> >
> > Finn
> >
>
> before I go and remove all of the archive.org stuff, can I get some feedback
> from other people as well on having this used? i.e. if keeping the old broken
> link in the kernel, how will people know to go to archive.org or any other
> archive site to read the old info?, as opposed to already having this in there
> so people can just click and go?..
>
> The idea to use archive.org came from this thread:
> http://amailbox.org/mailarchive/linux-kernel/2010/7/21/4596207/thread
> where there are people still wanting to read the old info.
If people want to read the old links, and they don't know about
archive.org, then they should. If you've seen one
"http://web.archive.org/web/*/foo/bar", you've seen them all. So this is
bloat in some sense.
As the web matures, and more and more information disappears from the web,
archive.org will become common knowledge (if it isn't already).
Applying your reasoning that "people are still wanting to read the old
info", a policy to accept patches like:
- http://foo/bar
+ http://web.archive.org/web/*/foo/bar
would imply another continual stream of patches when the domain foo
changes hands. Then you have to pach,
- http://web.archive.org/web/*/foo/bar
+ http://web.archive.org/web/YYYYMMDDHHMMSS/foo/bar
Then the problem becomes what is the correct YYYYMMMDDHHMMSS? The one
closest to the datestamp of submission of the patch? Or the datestamp from
the email that submitted the patch? When these questions arise, it becomes
a new burden on maintainers to determine the right version of the web page
in the archive, and whether or not the latest version is the best one.
So both of these (arguably) continuous streams of patches would become a
burden on maintainers and offer little or no benefit to those reading the
source code.
The benefit to end users is also dubious, because you're chasing web pages
that were abandoned, implying low value in the first place.
Though they move from one URL to another, the links that are valuable are
the web pages that are regularly updated. These are are the links that
need to be kept up-to-date. And I think your work in that direction is
valuable.
Thanks.
Finn
>
> Justin P. Mattock
>
>
next prev parent reply other threads:[~2010-09-22 2:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 4:18 [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-21 4:32 ` [PATCH]Update-broken-web-addresses-in-the-kernel Randy Dunlap
2010-09-21 4:51 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-21 4:52 ` [PATCH]Update-broken-web-addresses-in-the-kernel Matt Turner
2010-09-21 5:02 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-21 5:11 ` [PATCH]Update-broken-web-addresses-in-the-kernel Matt Turner
2010-09-21 5:17 ` [PATCH]Update-broken-web-addresses-in-the-kernel Finn Thain
2010-09-21 5:26 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-21 16:09 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-22 2:41 ` Finn Thain [this message]
2010-09-22 3:12 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-22 5:44 ` [PATCH]Update-broken-web-addresses-in-the-kernel Finn Thain
2010-09-22 6:08 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-21 5:20 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-21 5:22 ` [PATCH]Update-broken-web-addresses-in-the-kernel Dmitry Torokhov
2010-09-21 6:31 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-21 5:25 ` [PATCH]Update-broken-web-addresses-in-the-kernel Ben Pfaff
2010-09-21 6:32 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-21 9:50 ` [PATCH]Update-broken-web-addresses-in-the-kernel Finn Thain
2010-09-21 13:32 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-22 4:40 ` [PATCH]Update-broken-web-addresses-in-the-kernel Justin P. Mattock
2010-09-22 5:03 ` [PATCH]Update-broken-web-addresses-in-the-kernel Finn Thain
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=alpine.LNX.2.00.1009221205330.4570@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=blp@cs.stanford.edu \
--cc=dmitry.torokhov@gmail.com \
--cc=geert@linux-m68k.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mattst88@gmail.com \
--cc=rdunlap@xenotime.net \
--cc=trivial@kernel.org \
--cc=vapier.adi@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
all inboxes | Powered by JetHome®