Apparently, #GitLab now supports sending patches by email instead of having to navigate the wizard on the UI[1]. The downside is that they expect patches in email attachments, so no existing tools work because they have a bit of a snowflake implementation.
The whole point of "patches via email" is that it is a transport with a well-defined format for the payload. Using the same transport with a different payload negates all interoperability.
For months I’ve been contemplating writing an #XMPP GUI client on #Rust (with Unix-like platforms and #LinuxMobile as targets).
My main blocker is the lack of a polished toolkit. The majority of them don’t have good clipboard support and I don’t want an IM client where you can’t send images or files.
I’m gradually accepting that I’m going to need to write my own toolkit (and I really don’t want to).
@lig This is more of a Unix thing though; it's the parent process who has to define where to pipe stdout and stderr. The init system is, inevitably, the one spawning your services.
@lig I wouldn't consider "bloat" a feature TBH. I do agree that anyone staying systemd is superior should learn about alternatives (the same is true in any context TBH).
I don't see OpenRC handling any logging. Where does stdout/stderr for services end up?