[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJ2ouaz8BpQzLxwfeW8ZLMfdfoR7NVdSDHJDFGQbpbjA2A=pbg@mail.gmail.com>
Date: Fri, 28 Apr 2023 22:51:38 +0200
From: Jouke Witteveen <j.witteveen@...il.com>
To: netdev@...r.kernel.org, linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: update urls to Linux Foundation wiki
On Mon, Oct 10, 2022 at 9:08 PM Jonathan Corbet <corbet@....net> wrote:
>
> Jouke Witteveen <j.witteveen@...il.com> writes:
>
> > The redirects from the old urls stopped working recently.
> >
> > Signed-off-by: Jouke Witteveen <j.witteveen@...il.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(-)
Parts of this patch have been applied by now after being sent in by
others. I believe the rest still makes sense to apply. Shall I rebase
the patch and send it again? Or was there a reason for it to be left
behind half a year ago?
> > 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?
I don't know of any and indeed this patch only exists because working
URLs are better than broken ones.
>
> Thanks,
>
> jon
Regards,
- Jouke
Powered by blists - more mailing lists