

On this same train of thought: there’s also git sparse-checkout which uses the skip-worktree bit under the hood, and may have an easier interface. I’m not sure though, I haven’t used it yet.
On this same train of thought: there’s also git sparse-checkout which uses the skip-worktree bit under the hood, and may have an easier interface. I’m not sure though, I haven’t used it yet.
I haven’t seen git update-index --skip-worktree
mentioned yet. You can read about the motivation for this feature in the git scm docs.
I have used it in the past when a professor wanted us to clone repos for assignments that included some opinionated settings for VSCode that I didn’t want to use. Skipping the work tree for that directory allowed me to change or delete the config files without git complaining every time I pushed or pulled or whatever, and the changes I made remained local.
You could set up a couple git aliases to “freeze” and “thaw” your config files on the second drive.
I’m a baby dev trying to collect some brain wrinkles. Can you expand that last point? What’s the downside of client side decorations? What’s a better alternative?
The point is that there is now a credible fear that if Biden does not drop out, Trump wins.
Replacing the candidate at the top of the ticket this late is a hail Mary, but it could bring unenthusiastic voters back into the Democratic tent.
I didn’t realize HTC was back in the phone business.
I thought they sold off their mobile assets to Google in order to chase VR and crypto hype cycles.
Reddit Enhancement Suite.
It’s this frontend that makes Lemmy look like old Reddit.
I have the exact same little box for my HTPC in my living room.
It’s possible something went wrong during your install or configuration. I’m running a different distro, but I had to do very little tweaking or configuring of drivers, since the hardware is pretty standard.
Do you have any display output at all? Dropping into a tty or accessing your machine over ssh after boot at least gives you a starting point to debug.
Some tools that you can use to gather more info:
inxi
: prints out helpful summaries of system info for debugging.inxi --graphics
should give you some info to work with. My output tells me that I’m using the i915 kernel driver for display output.modinfo
: prints out kernel module info. The output is lengthy, so piping to a pager is helpful:modinfo i915 | less
journalctl --this-boot --priority=3
, or search for messages related to the i915 kernel module withjournalctl --this-boot --grep i915