[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <xmqq5ysa5193.fsf@gitster.g>
Date: Mon, 29 Nov 2021 09:18:32 -0800
From: Junio C Hamano <gitster@...ox.com>
To: Jani Nikula <jani.nikula@...el.com>
Cc: Eric Wong <e@...24.org>, Thorsten Leemhuis <linux@...mhuis.info>,
workflows@...r.kernel.org, linux-kernel@...r.kernel.org,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
Jonathan Corbet <corbet@....net>, git@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
Kees Cook <keescook@...omium.org>
Subject: Re: [RFC PATCH v1 1/1] docs: add the new commit-msg tags
'Reported:' and 'Reviewed:'
Jani Nikula <jani.nikula@...el.com> writes:
> From the RFC nitpicking department, ...
>
> Message-ID: (comment)
> <message-id@...mple.com>
Thanks for a fun piece; the (comment) is quite interesting.
I wasn't having fun with RFC nitpicking, though. I was reacting to
this part of the message I was responding to ...
>>> Fwiw, every mail and HTTP/1.x header parser I've looked at works
>>> case-insensitively. Also, I'm not sure if `g' is needed, actually...
... to say that "works case-insensitively" may not just be
empirically correct, but RFC backs him up, to Eric.
Powered by blists - more mailing lists