Message-ID's are used to identify and retrieve messages from the public-inbox archive on lore.kernel.org, so it's only natural to want to use memorable ones. Or maybe it's just me. Regardless, here's what I do with neomutt and coolname: If coolname isn't yet packaged for your distro, you can install it with pip: pip install --user coolname Create this file as ~/bin/my-msgid.py: #!/usr/bin/python3 import sys import random import string import datetime import platform from coolname import gener...| Konstantin Ryabitsev
At some point in the recent past, mutt changed the way it generates Message-ID header values. Instead of the perfectly good old way of doing it, the developers switched to using base64-encoded random bytes. The base64 dictionary contains the / character, which causes unnecessary difficulties when linking to these messages on lore.kernel.org, since the / character needs to be escaped as %2F for everything to work properly. Mutt developers seem completely uninterested in changing this, so pleas...| Konstantin Ryabitsev
While b4 started out as a way for maintainers to retrieve patches from mailing lists, it also has contributor-oriented features. Starting with version 0.10 b4 can: create and manage patch series and cover letters track and auto-reroll series revisions display range-diffs between revisions apply trailers received from reviewers and maintainers submit patches without needing a valid SMTP gateway These features are still considered experimental, but they should be stable for most work and I'd be...| Konstantin Ryabitsev
Once every couple of years someone unfailingly takes advantage of the following two facts: most large git hosting providers set up object sharing between forks of the same repository in order to save both storage space and improve user experience git's loose internal structure allows any shared object to be accessed from any other repository Thus, hilarity ensues on a fairly regular basis: https://github.com/torvalds/linux/blob/ac632c504d0b881d7cfb44e3fdde3ec30eb548d9/Makefile#L6 https://gith...| Konstantin Ryabitsev
Linux development depends on the ability to send and receive emails. Unfortunately, it is common for corporate gateways to post-process both outgoing and incoming messages with the purposes of adding lengthy legal disclaimers or performing anti-phishing link quarantines, both of which interferes with regular patch flow. While it is possible to configure free options like GMail to work well with sending and receiving patches, Google services may not be available in all geographical locales -- ...| Konstantin Ryabitsev
asciicast One of the side-effects of the recent UMN Affair has been renewed scrutiny of the kernel development process that continues to rely on patches sent via email. This prompted me to revisit my end-to-end patch attestation work and get it to the point where I consider it to be both stable for day-to-day work and satisfactory from the point of view of underlying security and usability. Goals of the project These were the goals at the outset: make it opt-in and don't interfere with existi...| Konstantin Ryabitsev
We have recently announced the availability of our new mailing list platform that will eventually take on the duties currently performed ...| Konstantin Ryabitsev
This is the second installment in the series where we're looking at using the public-inbox lei tool for interacting with remote mailing l...| Konstantin Ryabitsev
I am going to post a series of articles about public inbox's new lei tool (stands for "local email interface", but is clearly a "lorelei"...| Konstantin Ryabitsev
Many people know that you can PGP-sign git objects -- such as tags or commits themselves -- but very few know of another attestation feat...| Konstantin Ryabitsev
For the past few weeks I've been working on a tool to fetch patches from lore.kernel.org and perform the kind of post-processing that is ...| Konstantin Ryabitsev