Re: [PATCH net-next v3 0/8] net: dsa: realtek: variants to drivers, interfaces to a common module

Arınç ÜNAL
2024-01-20T22:13:53Z

On 17.01.2024 15:48, Linus Walleij wrote:
> On Wed, Jan 17, 2024 at 11:26 AM Arınç ÜNAL <arinc.unal@arinc9.com> wrote:
>> On 16.01.2024 00:54, Vladimir Oltean wrote:
>
>>> git format-patch --cover-letter generates a nice patch series overview
>>> with a diffstat and the commit titles, you should include it next time.
>>
>> Thanks a lot for mentioning this. I didn't know this and now that I use it,
>> it helps a lot.
>
> There are some even nicer tools you can use on top, i.e. "b4":
> https://people.kernel.org/monsieuricon/sending-a-kernel-patch-with-b4-part-1
>
> This blog post doesn't mention the magic trick:
> b4 prep --set-prefixes net-next
>
> And
> b4 trailers -u
>
> Which is what you need to make it an awesome net contribution
> patch series tool.

I've spent a day thinking I probably don't need this. I've spent the next
day giving it a go. I need this. Diffstat, the auto formatting of new
version change log, and linking to the previous version on the cover
letter, patch version comparison, and auto adding trailers features make my
life so much easier.

I've had trouble with every mail provider's SMTP server that I've ever used
for submitting patches, so the web endpoint is a godsend. It would've been
great if b4 supported openssh keys to submit patches via the web endpoint.
Patatt at least supports it to sign patches. I've got a single ed25519
openssh keypair I use across all my devices, now I'll have to backup
another key pair. Or create a new key and authenticate with the web
endpoint on each device.

Safe to say, I will submit my next patch series using b4. Thanks for
telling me about this tool Linus!

Arınç