>>> + $diagnostics .= "Missing a pair of parentheses
>>> '()' or a pair of double quotation marks (\"\").\n";
>>
>> Can such a message trigger any more thoughts and development ideas?
>
> No, I don't think so. '(" ... ")' is the minimum interface between analyser
> (check
On Sat, May 02, 2020 at 09:40:24PM +0200, Markus Elfring wrote:
>
>
> > + $diagnostics .= "Missing a pair of parentheses
> > '()' or a pair of double quotation marks (\"\").\n";
>
> Can such a message trigger any more thoughts and development ideas?
No, I don't think
>> Will the tolerance (and support) grow for such quotation character
>> alternatives?
>
> No.
Would you prefer to achieve a restrictive data format description?
>> * Which formula do you propose for the length calculation?
>
> None.
I imagine that such a view can increase the probability for
On Sat, 2020-05-02 at 21:40 +0200, Markus Elfring wrote:
> > The check doesn't support below formats and it will emit diagnostics info
> > for them:
[]
> Will the tolerance (and support) grow for such quotation character
> alternatives?
No.
> Does this information indicate a need to split possi
> The check doesn't support below formats and it will emit diagnostics info for
> them:
…
> Fixes: ba35f8588f47 (“ipvlan: Defer multicast / broadcast processing to a
> work-queue”)
…
> Fixes: 03f6fc6de919 ('ASoC: rt5682: Add the soundwire support')
Will the tolerance (and support) grow for such
According to submitting-patches.rst, 'Fixes:' tag has a little
stricter condition about the one line summary than normal git
commit description:
“...
Do not split the tag across multiple lines, tags are exempt from
the "wrap at 75 columns" rule in order to simplify parsing scripts
...”
And there i
6 matches
Mail list logo
