Hacker News new | ask | show | jobs
by Thrymr 4018 days ago
That loses a lot of information, though. If you want to bisect to find a particular bug, tracking it down to the merge is a good start, but I'd rather have the actual commit (from the maybe hundreds) that went into the merge. Sure, you can revert the feature, but what if you want to fix the bug?

Git history has a lot of commits. That's OK.

1 comments

Yes, the downside of a much more streamlined commit log is that we do throw out information.