Markus Elfring wrote:
> >> Would you insist on the usage of cover letters also for single patches?
> >
> > I would neither insist on it, nor prohibit it.
>
> It seems that you can tolerate an extra message here.
>
>
> > It simply does not make enough difference.
>
> Can it occasionally be a bit
>> Would you insist on the usage of cover letters also for single patches?
>
> I would neither insist on it, nor prohibit it.
It seems that you can tolerate an extra message here.
> It simply does not make enough difference.
Can it occasionally be a bit nicer to receive all relevant information
On Tue, Jun 27, 2023 at 06:22:47PM +0200, Markus Elfring wrote:
> >> How do you think about to put additional information below triple dashes
> >> (or even into improved change descriptions)?
> >>
> >> See also:
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentat
>> How do you think about to put additional information below triple dashes
>> (or even into improved change descriptions)?
>>
>> See also:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.4#n686
>
> Markus,
>
> Please go a
On Tue, Jun 27, 2023 at 08:08:19AM +0200, Markus Elfring wrote:
> > The thought was to put descriptions unsuitable for commit header in the
> > cover letter.
>
> How do you think about to put additional information below triple dashes
> (or even into improved change descriptions)?
>
> See also:
5 matches
Mail list logo
