K. Ryabitsev
@monsieuricon
Moderator
Posts
1649Following
216Followers
2190This 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
@biplanepilot well, maybe not "outlandish," keeping in mind its xenophobic roots?
1
1
1
K. Ryabitsev
monsieuricon
Looks like I may need to borrow my seat cushion when I exit the plane in Vienna, just so I have a personal flotation device with me.
0
0
7
K. Ryabitsev
monsieuricon
Reading about the debates reminds me of that scene in Rocky where he goes against Thunderlips.
0
0
1
K. Ryabitsev
monsieuricon
@kernellogger @linuxplumbersconf There go his plans to scuba in the Danuba.
0
0
2
K. Ryabitsev
monsieuricon
@ross No, not yet. I've been focused on infra/OS upgrades, so my b4 work is slower than expected.
0
0
1
K. Ryabitsev
monsieuricon
I was aware of patman before I started working on b4 contributor features, but I see them as targeting slightly different audiences. My goal is to solve several problems: 1. lower the entry barrier for newbies and occasional committers, 2. make it possible to submit patches without requiring a compliant SMTP server.
With the recent changes to public-inbox and the new set of features I'm planning for b4-0.15, we should be getting closer to the point where it's reasonable to send patches via pull requests and have them go through a full review cycle with lore.kernel.org acting as a fully transparent "messaging bus."
With the recent changes to public-inbox and the new set of features I'm planning for b4-0.15, we should be getting closer to the point where it's reasonable to send patches via pull requests and have them go through a full review cycle with lore.kernel.org acting as a fully transparent "messaging bus."
1
0
6
K. Ryabitsev
monsieuricon
Good overview of patman and b4 from Doug Anderson at Google.
https://www.youtube.com/watch?v=7B3nKmBoFoQ
https://www.youtube.com/watch?v=7B3nKmBoFoQ
1
5
3
K. Ryabitsev
repeated
repeated
Radicle
radicle@toot.radicle.xyz📢 Today, we are pleased to announce that Radicle 1.0 is ready for everyone to use!
After five months of feedback and 17 release candidates, we are finally ready to call this release stable.
Read the blog post for details, and give it a spin. 🎊
0
4
1
K. Ryabitsev
monsieuricon
Shamefacedly deletes an unanswered thread dating to February 2023 from his inbox.
In my head, an error message from qmail:
This is a permanent error; I've given up. Sorry it didn't work out.
In my head, an error message from qmail:
This is a permanent error; I've given up. Sorry it didn't work out.
0
0
7
K. Ryabitsev
repeated
repeated
Drew Fustini
pdp7@fosstodon.orgInteresting replies on kernel newbies from @gregkh and @monsieuricon
> What does "TIP" stand for in the repository
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/?
' "Thomas" "Ingo" "Peter", the original maintainers of that tree (i.e. the
x86 maintainers tree, which has now grown to other people and other
parts of the kernel.)'
https://lore.kernel.org/kernelnewbies/CAE7jHC-CCgLLc=0wvJg0uwcQ-nSJ5Xh9nR2PAS5+iAUgi-GiYw@mail.gmail.com/
1
1
2
K. Ryabitsev
monsieuricon
@losttourist Can confirm -- I have previously sent my nitrokey through a washing cycle and it's still working after overnighting in some silica gel crystals.
0
0
0
K. Ryabitsev
repeated
repeated
K. Ryabitsev
repeated
repeated
Greg K-H
gregkh
In non-CVE news, here's some fun hardware I got while visiting Hong Kong. It's not the snappiest laptop I've ever used, but it holds potential!
Kernel source is all public (there's a 6.1.y and 6.6.y tree at the moment), hopefully will start working on getting it all merged upstream to make it a proper platform for others to use.
Kernel source is all public (there's a 6.1.y and 6.6.y tree at the moment), hopefully will start working on getting it all merged upstream to make it a proper platform for others to use.
3
9
32