Today marks the day I officially converted my internal C
and bin
directories over to git
from subversion
. I have a set of personal tools I use (or just to test how things work) that I’ve kept in subversion.
Why?
Because the central repository was perfect for it. I did not care about distributed environment. I would always commit back to the central authority.
Why did I change?
Well, I do modify the code from different machines here and there, and I finally hit a merge conflict that is pretty much impossible to solve with subversion. Which caused me a couple of hours to get it back to a working state as subversion makes it very difficult to resolve nasty conflicts.
Thank God for git svn
as I needed to maintain the history as well.
Oh well, Goodbye subversion. It was fun while it lasted.
For my day off, I decided to implement passing a stack trace from start event to end event (to show the backtrace of the longest blocked areas).
I usually add this to my .bashrc
file to all my work machines.
alias reboot='echo "Wrong window idiot!"'
alias halt='echo "Wrong window idiot!"'
alias shutdown='echo "Wrong window idiot!"'
But I just learned, that I never added it to my Google workstation 😛
The blog on the responses from the Linux Plumbers survey is now published. https://lpc.events/blog/2022/index.php/2023/01/06/lpc-2022-attendee-survey-summary/
Continuing my Rust Rants :-)
It’s unfortunate that move
is a keyword. As I write my little programs, I found that that’s a common function name I use. Now I need to come up with something else. adjust ?
There’s gotta be a better way…
use std::env;
use std::path::Path;
fn usage(arg: &String) {
let path = Path::new(arg);
println!("usage: {} a b", path.file_name().unwrap().to_str().unwrap());
}
fn main() {
let args = env::args();
if args.len() < 3 {
usage(&args.collect::<Vec<String>>()[0]);
}
}
ANNOUNCE: new releases! trace-cmd 3.1.5 libtracecmd 1.3 libtracefs 1.6.3 libtraceevent 1.7