K. Ryabitsev 🍁
@monsieuricon
Moderator
Posts
2044Following
230Followers
2522This account is for Linux/Kernel/FOSS topics in general: #linux, #kernel, #foss, #git, #sysadmin, #infrastructure.
For my personal account, please follow @monsieuricon@castoranxieux.ca.
Montréal, Québec, Canada 🇨🇦🇺🇦
K. Ryabitsev 🍁
monsieuricon
Bah, I've recorded the video of submitting the patch using "b4 send", but I didn't think to check what the mic picks up when I'm typing on the keyboard. I apologize for any headaches caused to those listening via headphones.
If you wait a bit, there will be a text write-up on people.kernel.org that you can follow instead of watching the video.
https://www.youtube.com/watch?v=QBR06ml2YLQ
If you wait a bit, there will be a text write-up on people.kernel.org that you can follow instead of watching the video.
https://www.youtube.com/watch?v=QBR06ml2YLQ
0
4
9
K. Ryabitsev 🍁
monsieuricon
Not entirely surprisingly, attempting to record a "sending a Linux patch from scratch" tutorial video identified a couple of annoying crashers in b4 when some configuration parameters are missing (like, a [sendemail] section -- not identified in previous testing because everyone obviously has a [sendemail] section in their .gitconfig :)).
I'll release b4 0.11.1 with more helpful error messages tomorrow and try to re-record the video again.
I'll release b4 0.11.1 with more helpful error messages tomorrow and try to re-record the video again.
0
0
3
K. Ryabitsev 🍁
monsieuricon
@falktx Yes, you're the kind of person I'm looking for! I'm recording a quickie video of me submitting a basic typo fix to illustrate my workflow and I'd be interested in feedback.
0
0
8
K. Ryabitsev 🍁
monsieuricon
@fclc Yeah, you're probably not the person I'm looking for. :)
I aim to make patch workflows easier, but I'm afraid all other parts of Linux kernel contribution process are going to remain hard -- because programming kernels and getting everyone to agree is hard. :)
I aim to make patch workflows easier, but I'm afraid all other parts of Linux kernel contribution process are going to remain hard -- because programming kernels and getting everyone to agree is hard. :)
0
0
7
K. Ryabitsev 🍁
monsieuricon
Are you someone who has a simple fix for something in the Linux kernel, but haven't bothered submitting a patch because you find the email workflow daunting? Can be a bugfix, spelling correction, anything at all.
If so, I want to talk to you! I have tools that simplify this process quite a bit, but I need more feedback from people who aren't long-term Linux maintainers.
Please reach out, either via here or by emailing mricon@kernel.org.
If so, I want to talk to you! I have tools that simplify this process quite a bit, but I need more feedback from people who aren't long-term Linux maintainers.
Please reach out, either via here or by emailing mricon@kernel.org.
9
425
333
K. Ryabitsev 🍁
monsieuricon
@mattblaze I hope not. People getting news from social media was exactly the reason why so many things started going wrong.
1
0
0
K. Ryabitsev 🍁
monsieuricon
Um... whoever is running the "bluez test bot" on bugzilla.kernel.org should probably exclude bugs older than a certain age. Just sayin'.
https://bugzilla.kernel.org/show_bug.cgi?id=7
https://bugzilla.kernel.org/show_bug.cgi?id=7
0
3
5
K. Ryabitsev 🍁
monsieuricon
@notken High-five from someone who gets a lot of helpful mail about improving our corn growing business.
0
2
7
K. Ryabitsev 🍁
monsieuricon
Santa: So, have you been naughty or nice?
Me: Oh, I've been naughty, Santa.
Santa: Oh, really? And how so?
Me: When replying to emails, I've been writing below the "Please do not write below this line".
Santa: What kind of monster are you?
Me: Oh, I've been naughty, Santa.
Santa: Oh, really? And how so?
Me: When replying to emails, I've been writing below the "Please do not write below this line".
Santa: What kind of monster are you?
0
3
5
K. Ryabitsev 🍁
monsieuricon
b4 0.11.0 is available
Many improvements to the contributor-oriented features (b4 prep, b4 trailers, b4 send). If you haven't tried those out yet, please check them out, they are documented here:
https://b4.docs.kernel.org/en/stable-0.11.y/contributor/overview.html
Release announcement:
https://lore.kernel.org/tools/20221219213715.2qozw5emt5j7t3xr@nitro.local/
#b4
Many improvements to the contributor-oriented features (b4 prep, b4 trailers, b4 send). If you haven't tried those out yet, please check them out, they are documented here:
https://b4.docs.kernel.org/en/stable-0.11.y/contributor/overview.html
Release announcement:
https://lore.kernel.org/tools/20221219213715.2qozw5emt5j7t3xr@nitro.local/
#b4
0
3
8
K. Ryabitsev 🍁
monsieuricon
@jonmasters as usual, we get into the morass of key distribution, revocation, and trusting the infra. If you add a signed document like "I am userfoo@social.kernel.org" and add it to your profile, that doesn't actually certify every post you make. I can post things as any user on social.kernel.org, so I (or someone who hacks me) can impersonate anyone there.
I am currently leaning towards webfinger-level certification -- you can easily verify that mricon@kernel.org is actually monsieuricon@social.kernel.org, and I think this is good enough for most purposes.
I am currently leaning towards webfinger-level certification -- you can easily verify that mricon@kernel.org is actually monsieuricon@social.kernel.org, and I think this is good enough for most purposes.
0
0
2
K. Ryabitsev 🍁
monsieuricon
@dirkhh let's hope so! I'm guessing this is highly dependent on your immediate local reality. Where I am, using CCS chargers still requires fumbling with several cards and hoping for the best. :/
0
0
0
K. Ryabitsev 🍁
monsieuricon
@dirkhh Sadly, a widespread and *reliable* fast-charge network is still the core consideration for many, and until Chademo/CCS wars are over, Tesla's fast-chargers will remain a much better option hands-down.
0
0
0
K. Ryabitsev 🍁
monsieuricon
PSA: just having a DKIM-Signature: header in your email isn't really enough, unless it has a d= part matching your From: address.
E.g., this is good:
From: foo@example.com
DKIM-Signature: v=1; d=example.com; [...]
This, on the other hand, serves no real purpose outside of Google:
From: foo@example.com
DKIM-Signature: v=1; d=example-com.20210112.gappssmtp.com; [...]
When there is no DKIM alignment, DMARC-enforcing servers will fall back to only using the SPF record, which doesn't work at all with mailing lists unless they rewrite the From: header.
So, please-please properly set up your DKIM infrastructure if you send messages to mailing lists. Or at the very least don't put p=reject into your DMARC policy.
E.g., this is good:
From: foo@example.com
DKIM-Signature: v=1; d=example.com; [...]
This, on the other hand, serves no real purpose outside of Google:
From: foo@example.com
DKIM-Signature: v=1; d=example-com.20210112.gappssmtp.com; [...]
When there is no DKIM alignment, DMARC-enforcing servers will fall back to only using the SPF record, which doesn't work at all with mailing lists unless they rewrite the From: header.
So, please-please properly set up your DKIM infrastructure if you send messages to mailing lists. Or at the very least don't put p=reject into your DMARC policy.
0
0
5