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.
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.
OS stands for “Oh Shit!”
Notably for CPU only. And on other platforms they already did.
Broadcom would like to clarify that while using KVM for the CPU virtualization, they will continue to rely on all of the existing VMware virtual devices for graphics and other functionality. Also on both macOS and Windows they have migrated to the native CPU virtualization frameworks.
The follow-up quotes
In your specific case, the problem is your employer is on that list [of sanctioned entities]. If there’s been a mistake and your employer isn’t on the list, that’s the documentation Greg is looking for.
we should just write the code how it should be
Notably, that’s not what he says. He didn’t say in general. He said “for once, [after this already long discussion], let’s push back here”. (Literally “this time we push back”)
who need a secure OS (all of them) will opt to not use Linux if it doesn’t plug these holes
I’m not so sure about that. He’s making a fair assessment. These are very intricate attack vectors. Security assessment is risk assessment either way. Whether you’re weighing a significant performance loss against low risk potentially high impact attack vectors or assess the risk directly doesn’t make that much of a difference.
These are so intricate and unlikely to occur, with other firmware patches in line, or alternative hardware, that there’s alternative options and acceptable risk.
Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug.
I wasn’t aware the GitHub terms of service explicitly grant / require you to grant permission to fork [within GitHub].
GitHub ToS section License Grant to Other Users
By setting your repositories to be viewed publicly, you agree to allow others to view and “fork” your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).
If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub’s functionality (for example, through forking). […] If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.
Valve is generously providing backing for two critical projects that will have a huge impact on our distribution: a build service infrastructure and a secure signing enclave.
What is Tails?
and Tails, a portable operating system that uses Tor
You are going to get lots of downvotes, and this comment will too.
👀
Hahahahahahahahahahaha
(Pause for breath)
Hahahahahahahahahahaha
Was that tone really necessary? I would have liked your comment more without this part.
hard to compete against sunshine
I’m using Sunshine and Moonlight to stream my PC to my TV too
German-based SUSE just extended long-term support for Linux Enterprise 15 until July 2037. […] 13 years from now […] that’s […] 19 years after 2018, which is when Linux Enterprise 15 was first released.
pretty good
Time to migrate to Funnertoo
They wrote they’re using . as placeholder commit messages.
I use f for such [f]ollowup/[f]ixup commits, and a for [a]dditional code/components/changesets. Both keys are trivial to enter. When cleaning it up after, f commits are typically squashed into previous ones, and a commits get a description and/or serve as a base for squashing.
I can see . working well as well, but having a more obvious character (with vertical height/substance) seems preferable.
You don’t see the point of making use of shortcuts?
It’s just them with shortcuts, they didn’t see the point of m
😏
I had never heard of opkg. I looked it up:
Wikipedia has no dedicated pages for either of them. I guess they’re quite niche.