From: Stephen Hemminger <stephen@networkplumber.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Jouke Witteveen <j.witteveen@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] Documentation: update urls to Linux Foundation wiki
Date: Mon, 10 Oct 2022 12:29:13 -0700 [thread overview]
Message-ID: <20221010122913.6a91b117@hermes.local> (raw)
In-Reply-To: <87v8orpkda.fsf@meer.lwn.net>
On Mon, 10 Oct 2022 13:08:17 -0600
Jonathan Corbet <corbet@lwn.net> wrote:
> Jouke Witteveen <j.witteveen@gmail.com> writes:
>
> > The redirects from the old urls stopped working recently.
> >
> > Signed-off-by: Jouke Witteveen <j.witteveen@gmail.com>
>
> I see the LF has done its annual web-site replacement; I have no idea
> why they are so enamored with breaking URLs...
>
> Anyway, This is networking documentation, so it should go to the folks
> at netdev [CC'd] rather than me.
>
> > Documentation/networking/bridge.rst | 2 +-
> > Documentation/networking/dccp.rst | 4 ++--
> > .../networking/device_drivers/ethernet/intel/ice.rst | 2 +-
> > Documentation/networking/generic_netlink.rst | 2 +-
> > MAINTAINERS | 2 +-
> > net/ipv4/Kconfig | 2 +-
> > net/sched/Kconfig | 2 +-
> > 7 files changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/Documentation/networking/bridge.rst b/Documentation/networking/bridge.rst
> > index 4aef9cddde2f..c859f3c1636e 100644
> > --- a/Documentation/networking/bridge.rst
> > +++ b/Documentation/networking/bridge.rst
> > @@ -8,7 +8,7 @@ In order to use the Ethernet bridging functionality, you'll need the
> > userspace tools.
> >
> > Documentation for Linux bridging is on:
> > - http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge
> > + https://wiki.linuxfoundation.org/networking/bridge
>
> So this page is full of encouraging stuff like:
>
> > The code is updated as part of the 2.4 and 2.6 kernels available at
> > kernel.org.
>
> ...and tells us about an encouraging prototype implementation in 2.6.18.
> I'd apply the patch because working URLs are better than broken ones,
> but I also question the value of this material at all in 2022... there
> should be better documents to link to at this point?
This is ancient networking wiki.
I took old stuff put it on wiki back when I was working at LF
but never updated since then.
next prev parent reply other threads:[~2022-10-10 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221001112058.22387-1-j.witteveen@gmail.com>
2022-10-10 19:08 ` [PATCH] Documentation: update urls to Linux Foundation wiki Jonathan Corbet
2022-10-10 19:29 ` Stephen Hemminger [this message]
2023-04-28 20:51 ` Jouke Witteveen
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=20221010122913.6a91b117@hermes.local \
--to=stephen@networkplumber.org \
--cc=corbet@lwn.net \
--cc=j.witteveen@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 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).