Re: Weird mangling of a commit log entry in gitweb summary

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-www(at)lists(dot)postgresql(dot)org
Subject: Re: Weird mangling of a commit log entry in gitweb summary
Date: 2022-07-18 14:01:37
Message-ID: 2606d71f-a940-8191-1123-7a375e832766@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On 7/18/22 4:37 AM, Julien Rouhaud wrote:
> On Mon, Jul 18, 2022 at 10:27:47AM +0200, Magnus Hagander wrote:
>>
>> AFAICT this is not functionality that can be turned off, it's all
>> hardcoded both in what it searches and when it does it. :/
>>
>> I doubt it's worth forking and maintaining a fork just to handle this
>> situation given how seldom it shows up.
>
> +1, especially since it was introduced 17 years ago and this is probably the
> first time someone notice it in our instance.

Maybe it's worth reporting upstream? It seems like it's doing something
very opinionated that may not make sense to projects using git.

Jonathan

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message MichaelDBA 2022-07-18 14:29:46 Re: Wiki editor request
Previous Message Joe Conway 2022-07-18 13:09:56 Re: Wiki editor request