4 ms·

Without a clean history it takes longer to find which commit changed things and why.

• recursive 6y ago
  I believe I've really only needed to do that once. git bisect handled it in about 10 minutes IIRC. It's hard for me to imagine how I could achieve a net time savings against that level of commit-hunting.
  • jamienicol 6y ago
    I envy you then. I spend a great deal of time looking through history to find bugs. An unclean history is less likely to work well with bisect too, as the individual commits may be broken.
    • Supermancho 6y ago
      > I spend a great deal of time looking through history to find bugs. You mean when where and how a change was introduced? I dont think bugs are located in the history, since bugs are operational failures on a deployed branch.
      • jamienicol 6y ago
        Yes, I phrased that badly. Let's say looking through history to understand the context of when bugs were introduced and how to fix them