<SiFuh_>
No that one we were discussing was another patch of mine, but it was not the runlevel fix.
<SiFuh_>
There are multiple entries I pushed throughout the past. But the important one I can't find it. Not sure why, because it is clearly written in.
<farkuhar>
SiFuh_: You can view the repo snapshot at the time of the very first commit by jw, 20 years ago. If your runlevel-switching code isn't present there, then it had to have been added by one of the 30 commits in the log.
<SiFuh_>
I have
<SiFuh_>
Anyways it isn't important. I think I brought it up because beerman thinks CRUX can't function without him and that I do nothing but complain. Hahaha
<SiFuh_>
He always falls on it to himself like he is the king and everyone else are plebs.
<farkuhar>
SiFuh_: I just wanted to confirm how long it actually took for your patch to be merged. Was it really 18 years, or did your runlevel-switching code first appear in the repo even earlier?
<SiFuh_>
Hmm it was 18 years. I know because I told them at the time.
<SiFuh_>
I had it done I think 2017 or 2018. I think 2018 because of the bitcoin crash was around that time.
<SiFuh_>
farkuhar: By the way, what is with the two padlocks over the last two commits?
<farkuhar>
SiFuh_: padlock is the symbol that Gitea uses to indicate a tagged commit (maybe the tag needs to be GPG-signed too).
<SiFuh_>
farkuhar: Maybe it was the mount options that were causing the issue for 18 years.
<SiFuh_>
I'd have to pull up the logs from 2018 and check probably.
<SiFuh_>
We don't want to build the Linux distribution for the masses <-- farkuhar Hehe "We want to build it for beerman"
<farkuhar>
SiFuh_: git-bisect(1) is a tool you can use to locate the commit where your patch was merged. Give it a starting commit (where the old code is still visible), an ending commit (where your code appears), and let it perform a binary search.
<SiFuh_>
farkuhar: Haha, I have better things to do to be honest
<SiFuh_>
Trying to plan a jungle trip with the sour-faced niece. She's the only one I like. She likes camping and actually tries to do suff.
<SiFuh_>
stuff
<SiFuh_>
The others are useless bums that sit around and expect to be waited on hand and foot.
<farkuhar>
Hush! Don't say you have better things to do in a public forum. beerman might use it as ammunition to accuse you of being insufficiently helpful to the project.
<SiFuh_>
I've pulled my fair share of the work.
<SiFuh_>
Apparently I am not allowed to tell people their scripts are broken. It's called complaining and not assistance.
<farkuhar>
I've been thinking about one of your recent comments, that perhaps the core team has lost their passion and are just going through the motions. "they ain't having fun" as darfo put it. Once the passion is gone, quality control inevitably goes downhill (as you discovered with FreeBSD in 2004).
<SiFuh_>
I think so. It appears more and more apparent the less jue and jaeger step in
<SiFuh_>
Also the fact a newbie can do what he wants with no opposition from the dev team is also a big give away
<farkuhar>
Heh, does he even have the humility to identify as a newbie? pitillo is a better example of that kind of humility.
<SiFuh_>
Yeah, being humble can go a long way
<farkuhar>
anthropologist David Graeber on why he got fired from Yale: "In extremely hierarchical environments, being nice is often seen as impertinent or subversive---at least, if one is equally friendly and sympathetic to everyone."