From: Ray Lee <ray-lk@madrabbit.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: "David S. Miller" <davem@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.4 patch] NET_IPIP help: remove no longer available URL
Date: Mon, 12 Jul 2004 08:08:43 -0700 [thread overview]
Message-ID: <1089644922.9086.45.camel@orca.madrabbit.org> (raw)
In-Reply-To: <20040712112826.GQ4701@fs.tum.de>
On Mon, 2004-07-12 at 04:28, Adrian Bunk wrote:
> > How about updating the URL instead:
> >
> > http://web.archive.org/web/19990420203353/http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html
>
> This URL is too long for one line.
<nod> Good point, but trivially solved: http://tinyurl.com/5sm9w
> Besides this, it's nearly 8 years old and therefore not in any respect
> up-to-date
Just because it's old doesn't mean it's out of date. Have you read the
webpage in question? The majority of the page simply explains what
mobile-IP *is* on a primer level, and how it might be used. That hasn't
changed.
> (and if it's only in a web archive, it will never be updated).
That's a half-empty worldview. You should be saying "Yay! Since it's on
the wayback machine, the URL will always be good!"
If this is really a problem, we could create a WikiPedia entry for it.
However, the page is on the level of a long dictionary definition or an
encyclopedia entry, and so it's not much more out of date than most
RFCs, for example.
Ray
next prev parent reply other threads:[~2004-07-12 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 3:48 [2.4 patch] NET_IPIP help: remove no longer available URL Ray Lee
2004-07-12 11:28 ` Adrian Bunk
2004-07-12 15:08 ` Ray Lee [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-10 19:34 Adrian Bunk
2004-07-12 0:50 ` David S. Miller
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=1089644922.9086.45.camel@orca.madrabbit.org \
--to=ray-lk@madrabbit.org \
--cc=bunk@fs.tum.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.