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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, 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 11:42:07
Message-ID: CAApHDvq5f+4ee-YOyki3s8=Z-qF2KTLFynjw-ucFRocPbS-GHw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 19 Sept 2025 at 23:05, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> On 19.09.25 10:22, Álvaro Herrera wrote:
> > There are two things we could do. One is to simply restrict `git blame`
> > to authenticated users; this shouldn't be_too_ bad. But if we don't
> > want that, we could put the bot checker javascript tricks in front of
> > `blame`. In fact maybe we could have the best of both worlds: you get
> > the javascript check if you're not authenticated, but nothing if you
> > are. I'm not sure how easy it is to implement this though.
>
> Or just disable git blame. Who needs to run that through the website?

I'd vote for getting rid of the blame if it could buy us back enough
CPU cycles to have diff working again. I personally miss not having
diff. I found it convenient when following links to see what's been
changed from the pgsql-committers list.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tender Wang 2025-09-19 11:44:56 Use opresulttype instead of calling SearchSysCache1() in match_orclause_to_indexcol()
Previous Message David Rowley 2025-09-19 11:37:48 Re: Fix typo in comment of match_orclause_to_indexcol()