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

"Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
> If the main concern is lack of diff - which cgit gives us back, and the
> main objection is the tab-size patch (in previous email)[1], is there
> any objection to moving forward with updating the URLs after this patch
> is applied (which I can't do, as I don't have privileges to that server)?

Not here.

> If there are objections, I'm fine to wait until after the release to
> re-open discussion.

My first thought about scheduling was "best not in the middle of the
18.0 release cycle". However, I don't know of any actual connection
between gitweb/cgit and the release-making tasks. My second thought
was "the point here is to cut server load, and maybe we need that to
happen before the anticipated traffic spike on Thursday". There
might not be any connection there either, but if there is, agreed
to get it done sooner not later.

regards, tom lane