Junio C Hamano <gitster@xxxxxxxxx> writes: > In any case, that is an appropriate thing to say in a commit that > fixes use of such a construct, but not a commit that uses the right > constuct from the get-go. > > I have to say that the [4/4] in the previous round, i.e., fc87b2f7 > (add-patch: render hunks through the pager, 2024-07-25) in my tree, > is better than this version. I do recall that you once had a version where the code violates the guidelines (and breaks dash) in one patch, and gets fixed in another patch in the same series. The above material would be a perfect fit in the proposed log message of the latter step. If we spent so much effort and digging to figure out exactly how it breaks with which shell, a separate patch to fix, primarily to document the fix, would have made sense. But the latest squashes the two and avoids making the mistake in the first place, eliminating the need for a documented fix. We generally prefer to do so to avoid breaking bisection (and the recommendation to keep the fix separate so that we can document it better was made as an exception), so squashing them into one is fine. But if we commit to that approach to pretend that there was no silly mistake, we should be consistent in pretending that is the case.
