Re: Having postgresql.org link to cgit instead of gitweb

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Having postgresql.org link to cgit instead of gitweb
Date: 2025-09-19 14:23:39
Message-ID: CAH2-WzkYFyU9v+bNeePdYjNp+wOx2dDQs7yb=NxC1ieoA_S_bg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 18, 2025 at 9:12 PM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
> While prepping the website for the PG18 GA, I stumbled on the inability
> to access parts of commits through the gitweb links, specifically
> hitting 429 status code errors (this seems to be intermittent). After
> some briefing on why it's disabled and how this isn't an issue with
> cgit, I prepped a patch for postgresql.org (the main website) that would
> update the git.postgresql.org reference to use cgit instead of gitweb.

cgit messes up indentation by showing 8 space tabs (not 4 space tabs)
-- that's certainly not ideal.

I understand that the same problem was fixed within gitweb by patching
the source code.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-09-19 14:25:52 Re: PG 18 relnotes and RC1
Previous Message Nathan Bossart 2025-09-19 14:19:48 Re: fix obsolete references to postgres.h in comments