• 0 Posts
  • 13 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle
  • If you’re wondering, I’d like to not be driving a Tesla. But it’s paid off, worth basically nothing in resale, and I got it as a CPO with free charging and autopilot for life. It costs Tesla money to keep it.

    Honestly just put a bunch of anti-Elon bumper stickers on your car and keep it until the battery shits the bed, it will be worth more as scrap metal. It’s costing you nothing and actively costing Tesla something.

    I get the stigma of having a Tesla, but some people did in fact buy it before Elon’s fascist tendencies were widely known. Its the people who buy one now after knowing how much more of a piece of shit he is that piss me off (like one of my neighbors who got a Tesla recently).

    If you have a Cybertruck though, fuck you, I hope your $100k+ death trap bursts into flames after a slight pothole taking you with it. Your car is actively making the roads less safe and you knew who you were buying it from.






  • Inside git’s internal plumbing folder, git holds a file with the branch name and all of the references (files and changes) for that branch.

    When you make a new branch git will update its internal plumbing checking to see if the new branch already exists, updates its references to the new branch if it doesn’t (all held internally in a case sensitive way). It will then make that new branch file, git has already checked that the case senitive name for the branch doesn’t exist internally, so it should be good to go.

    Part of its process is creating that internal branch file… But wait!

    Windows doesn’t have case sensitive naming so when it tries to make that new branch file it will overwrite the old one (since it shouldn’t exist by git’s own reference!) All of the files and references for it now get nuked.

    Now you’re at best back to wherever that originally named branch came from, at worse your .git folder is properly borked.