4 ms·
Bisect also becomes useless because of large commits. Even if you find the commit, the change it introduces can be so large you don't git much improvement. Git
by _ikke_ 10y ago
Bisect also becomes useless because of large commits. Even if you find the commit, the change it introduces can be so large you don't git much improvement.
Git allows you to clean up your feature branches to prevent these kind of fix commits.
Look at git.git. They don't require people to squash all their commits into a single patch, but still every patch should be compilable.
- jerf 10y ago"As long as I can bisect, I don't much care about the details." If I can't bisect, I don't approve. So, by simple logic based on the premise you supply, I also disapprove of large commits. My point may not be what you expected prior to reading.
- juped 10y agoThen your comment makes no sense in context, because you replied to my complaint that people lose information by doing these giant squash merges and having no nontrivial graph structure in their main project history.
- jerf 10y agoThere are positions other than the extremes. My position makes sense, yes, in context too.