I’m just glad we didn’t end up with this one (seen in the ticket)

Damn, sad story behind the color

I had never heard of opkg. I looked it up:

opkg: Fork of ipkg lightweight package management intended for use on embedded Linux devices;

ipkg: A dpkg-inspired, very lightweight system targeted at storage-constrained Linux systems such as embedded devices and handheld computers. Used on HP’s webOS;

Wikipedia has no dedicated pages for either of them. I guess they’re quite niche.

deleted by creator

I’ve used it at work. But the manual management/maintenance of a commit list makes it practically infeasible. I’ve use it for bit cleanup commits, but not since. When blaming, the previous revision is just one click away anyway. The maintenance doesn’t seem worth the effort.

I guess a commit message tag and script that generates it automatically could make it viable. But I’ve not found the need to yet.

Installable alternative: https://zealdocs.org/

Given that it is high level, I assume you did not want to include this. I’ll mention it here in a comment either way. Text form in the commit message.

I really like using conventional commit messages and introduced it in my projects. We defined a few types, and more leniently choose optional scopes. It’s very useful for categorizing and skimming through commit lists, and for generating changelogs/release notes. `fix(account): Use correct hasing xy"

Consistent imperative form is important to me too. The commit message examples talks about “Summary of changes”, which has no verb, and so, may mislead to a different undesirable form of summarizing changes. (“Change xy” instead of “changed xy” or “[now] does xy [at runtime]” or “did z”.)

I didn’t fully read it, only skimmed, so excuse me if I missed mentions of the commit message text form. It seems very elaborate otherwise.

My browser has a default font size of 18 set. The site overrides that with a default base font size of 12px, then increases it to 13px for content text. That’s way too small for me on my screen. At least to read it comfortably. Or for people who need more accessible text/font.

The field is incredibly broad. Choose a field or employer or project that’s not doing that an you’re fine.

Are you sure? I’m not very active in that ecosystem, but if that was prevalent in the past, surely there’s still tutorials and stuff out there that people would follow and create such projects even today?

More than that, it seems to me that the official python docs for packaging [still] talks about setup.py. Why would people not use that?

got it; arse

It would certainly be an issue if you didn’t have one

The problem was named after an incident in 1996 in which AOL’s profanity filter prevented residents of the town of Scunthorpe, North Lincolnshire, England, from creating accounts with AOL, because the town’s name contains the substring “cunt”.

haha

those are terms, this is substrings within words

I haven’t seen branches or variables being called arse

Then again, I do like to catch exceptions as up so I can throw up

Simple changes require only simple reviews.

Responsibility is shared. It’s not one or the other.

Many people don’t know what they’re doing. That’s kind of expected. But a tool provider and seller should know what they’re doing. Enabling people to behave in a negative way should be questioned. Maybe it’s a consequence of enablement, or maybe it’s bad design or marketing. Where criticism is certainly warranted.

Commit with Co-authored-by: Copilot

or maybe better --author=Copilot

It would certainly help evaluate submissions to have that context

he l p

looks like a multi-threading or concurrency issue

each function has its own independent metal toggle switch

one steering wheel to steer left, and one to steer to the right

they want to push a lot of buttons on those controls

LOL

Even with a lot of buttons available, good videogame controls are simple and narrow. Natural combinations add depth without overcomplicating things.

OS stands for “Oh Shit!”