• 0 Posts
  • 21 Comments
Joined 2 years ago
cake
Cake day: July 20th, 2023

help-circle

  • Yep. I got a thinkpad a couple years ago that was enough of a deal that I forgave its nvidia GPU. I followed the documentation on how to connect a repo controlled by nvidia, and since then: a) the actual GPU appears to be used, but b) maximum brightness on the screen is significantly dimmer, and games run worse than they did when the GPU wasn’t actually used.

    And also I use KDE. I’m still on X11, though, so I didn’t complete the set.




  • Yeah. “I use OpenSUSE tumbleweed, but have reasons I’ve been thinking about switching. I consistently hear that mint is a good place to start, or maybe pop!os if you’re looking to run games”

    I don’t actually even say the first sentence unless the question was “what do you use?”

    Sometimes, if it’s clear they’re trying to revive very old hardware I might help them search for something built around being lightweight.

    I’m mostly happy with tumbleweed, except that I have the nvidia repo set up and am convinced that it’s causing issues. One of these days I’ll look into how to try the nouveau drivers and/or how to get from my current setup to dualbooting pop!os without disrupting things I need for work.

    Also, an update straight up broke emacs while i was in crunch time once, but I learned to be more careful about my update timing.











  • I’m guessing you don’t mean commits that actually bring updates from a different branch in? I’m responsible for a bunch of commits that catch my feature branch up to main and a couple that bring my branches into main.

    If we were working on the same project, what would you want to see for those? This is hosted on a private gh repo, but it’s a small shop and we were working on a tight deadline for an MVP release and were not using PRs for the stuff I was working on.

    The boss (co-owner of the business) is the Sr dev on the project and until recently was the only sr dev in the whole shop. I actually don’t think he has experience with using git in a team context.

    One of my other tasks is working on internal docs (which didn’t exist before I joined the team) that would include git best practices for branching strategies and commit messages, so I’m interested in what folks who have more experience than I do would like to see as I try to nudge the team practices.


  • Git won’t let the second person push if their commit history doesn’t line up with the origin branch.

    It should be trivial to do a git pull --rebase to move your new commit after the upstream version, but as far as I can tell, no one on my current project remembers this (or perhaps they’re using gui tools or something). Our log is full of “merge origin/main onto main”.