From: Jeff King <peff@peff.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Christian Couder <christian.couder@gmail.com>, git@vger.kernel.org
Subject: Re: The sad state of git.wiki.kernel.org
Date: Tue, 7 Feb 2023 13:09:58 -0500 [thread overview]
Message-ID: <Y+KT9pHivnUyyu0K@coredump.intra.peff.net> (raw)
In-Reply-To: <20230206214101.fe6rismtfzv4k75n@meerkat.local>
On Mon, Feb 06, 2023 at 04:41:01PM -0500, Konstantin Ryabitsev wrote:
> On Sat, Feb 04, 2023 at 03:03:16PM +0100, Christian Couder wrote:
> > > > # Should it be archived as a static site?
> > > >
> > > > It's possible to turn git.wiki.kernel.org into a static site with a large
> > > > header on every page that it contains historical archival information, with a
> > > > link to https://git-scm.com/doc
> > >
> > > This would be my preference, just because some of the old content may
> > > still have value. Some pages (like old gsoc stuff) would better redirect
> > > to git.github.io, but it is probably not worth the time to even try to
> > > classify pages.
> >
> > This would be my preference too. I agree that some old content might
> > still have some value. We could also move or redirect some old content
> > to git.github.io, but I am not sure it's worth the time either.
>
> Okay, here's what I have:
>
> https://archive.kernel.org/oldwiki/git.wiki.kernel.org/
>
> It's just a static scrape excluding all Special: and User: pages, and carrying
> a very large "OBSOLETE CONTENT" warning.
That looks just fine to me. Thanks for taking care of this!
-Peff
next prev parent reply other threads:[~2023-02-07 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 18:22 The sad state of git.wiki.kernel.org Konstantin Ryabitsev
2023-02-03 19:43 ` Junio C Hamano
2023-02-04 11:27 ` Jeff King
2023-02-04 13:13 ` Andrei Rybak
2023-02-04 14:03 ` Christian Couder
2023-02-06 21:41 ` Konstantin Ryabitsev
2023-02-07 11:53 ` Christian Couder
2023-02-07 18:09 ` Jeff King [this message]
2023-02-09 21:31 ` Konstantin Ryabitsev
2023-02-09 21:46 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+KT9pHivnUyyu0K@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).