Re: sys/modules/sdio broken in .svn_revision 348842 'opt_cam.h' not found

> On Jun 17, 2019, at 7:46 PM, Julian H. Stacey <jhs_at_berklix.com> wrote:
> 
>>> 
>>> Stop.
>>> make[3]: stopped in /usr/src/usr.bin/mkesdb_static
>>> 
>>> A double waste of CPU & human time & power in a hot office.
>>> Commit bits used to be suspended for un-buildable code. I'll boot
>>> stable.
>> 
>> Since you seem to be so focused on mean-spirited criticism of others,
>> I'm sure you'll understand when I ask...
>> 
>> Have you *seriosly* been using and building freebsd this long and you
>> don't know that an opt_*.h file is generated as part of the build and
>> exists only in the object directory, so that searching for it under
>> /usr/src or /usr/include would be... let's see, how did you put it?...
>> Oh yeah: A double waste of CPU & human time.
> 
> Personal noise is irrelevant.
> 
> Facts: 
> Unchecked commits broken make buildworld twice, 
> Time was wasted by bad commits.  
> My time ran out. 
> Current does not benefit from commits that break buildworld.
> I (like a friend before) must switch to stable to avoid breakage. 
> 
> Time was, ~25 years back, when FreeBSD commiters who screwed
> the build were awarded a conical hat & took a one week holiday. A
> mild rebuke for wasting people's time, & a short refreshing
> break to go smell fresh air. No not coffee, but fresh air.

I’ve been following FreeBSD since 1992, before it was even called
FreeBSD, and I was reflecting on the “old days” recently.  You know
what?  The old days sucked; I hold no romance for them.  There was
rampant passive-aggressive hostility, toxicity and shaming was
accepted and encouraged, and the community was pretty much an
insular and exclusionary clique. Mistakes were to be feared, not
learned from.  Any mistake was equated with a personal moral failing.
Yeah, good technical work was done, but at the expense of quickly
alienating and driving away many good people who didn’t want to
put up with all of that bullshit.

There’s no denying that it’s frustrating when a bug is introduced,
especially when it causes lost time and productivity.  Passively
accusing people of being lazy or incompetent (see your “Unchecked
commits” comment) doesn’t help fix that though.  If anything, it burns
out and drives away the people who are in the best position to fix the
problems. It doesn’t make the community or the code better in the
long term, even if you think that it’s motivating people in the short
term.

Please take your conical hat somewhere else and do something
productive and positive with it, I don’t want the toxicity in my
FreeBSD community anymore.

Thanks,
Scott