Re: Having postgresql.org link to cgit instead of gitweb
От | David Rowley |
---|---|
Тема | Re: Having postgresql.org link to cgit instead of gitweb |
Дата | |
Msg-id | CAApHDvq5f+4ee-YOyki3s8=Z-qF2KTLFynjw-ucFRocPbS-GHw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Having postgresql.org link to cgit instead of gitweb (Peter Eisentraut <peter@eisentraut.org>) |
Ответы |
Re: Having postgresql.org link to cgit instead of gitweb
|
Список | 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 по дате отправления: