Large sheep the size of a small sheep! Late 20’s queer sysadmin, release engineer and programmer. Likes tea, DIY, and nerd stuff. Follow requests generally accepted but please have a filled out profile first!

  • 0 Posts
  • 2 Comments
Joined 2 years ago
cake
Cake day: December 4th, 2022

help-circle

  • @agressivelyPassive @technom That’s a self-fulfilling prophecy, IMO. Well-structured commit histories with clear descriptions can be a godsend for spelunking through old code and trying to work out why a change was made. That is the actual point, after all - the Linux kernel project, which is what git was originally built to manage, is fastidious about this. Most projects don’t need that level of hygiene, but they can still benefit from taking lessons from it.

    To that end, sure, git can be arcane at the best of times and a lot of the tools aren’t strictly necessary, but they’re very useful for managing that history.