Re: Having postgresql.org link to cgit instead of gitweb - Mailing list pgsql-hackers

From David Rowley
Subject Re: Having postgresql.org link to cgit instead of gitweb
Date
Msg-id CAApHDvq5f+4ee-YOyki3s8=Z-qF2KTLFynjw-ucFRocPbS-GHw@mail.gmail.com
Whole thread Raw
In response to Re: Having postgresql.org link to cgit instead of gitweb  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: Having postgresql.org link to cgit instead of gitweb
List pgsql-hackers
On Fri, 19 Sept 2025 at 23:05, Peter Eisentraut <peter@eisentraut.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



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Fix typo in comment of match_orclause_to_indexcol()
Next
From: Tender Wang
Date:
Subject: Use opresulttype instead of calling SearchSysCache1() in match_orclause_to_indexcol()