From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org, Jon Turney <jon.turney@dronecode.org.uk>
Subject: Re: cygwin-packages gitweb to cgit rewrite
Date: Thu, 8 Feb 2024 12:26:36 +0100 [thread overview]
Message-ID: <20240208112636.GI25554@gnu.wildebeest.org> (raw)
In-Reply-To: <ZcSehH-xjTIkdAoj@calimero.vinschen.de>
Hi Corinna,
On Thu, Feb 08, 2024 at 10:27:32AM +0100, Corinna Vinschen via Overseers wrote:
> On Feb 8 00:38, Mark Wielaard via Overseers wrote:
> > For now I redirected https://cygwin.com/git-cygwin-packages/ and
> > https://cygwin.com/git/cygwin-packages/ to
> > https://cygwin.com/cgit/cygwin-packages/
> >
> > This is just for the overview pages. All other subpages (and git
> > repos) are still accessible.
> >
> > Rewriting those using Arsen's script [*] is a little tricky, unless we
> > rewrite all cygwin/sourceware/gcc gitweb urls.
> >
> > Please yell and scream if I broke something.
>
> Didn't we want to move sware to cgit anyway? I think this is a good
> move, given how much faster cgit works. The Cygwin homepage points
> to the cgit web pages for quite some time already, at least as far
> as the newlib-cygwin repo is concerned.
Yes, and we did "move", we now have https://cygwin.com/cgit
https://sourceware.org/cgit https://gcc.gnu.org/cgit and
https://git.dwarfstd.org
But the old links and https git transport backend still need to keep
working on the old gitweb /git/ locations.
I would love to "overlay" Arsen's script to rewrite all the old gitweb
URLs to cgit, but I haven't found a good way to do that in stages (so
e.g. just for cygwin-packages first). Because we multiplex our gitweb
calls through the /etc/gitweb.conf setup. We need to find a way to do
it through /etc/httpd/conf.d/gitweb.conf
Cheers,
Mark
next prev parent reply other threads:[~2024-02-08 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 23:38 Mark Wielaard
2024-02-08 9:27 ` Corinna Vinschen
2024-02-08 11:26 ` Mark Wielaard [this message]
2024-02-08 11:36 ` Frank Ch. Eigler
2024-02-08 19:42 ` Jon Turney
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=20240208112636.GI25554@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=jon.turney@dronecode.org.uk \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).