"Michael Rappazzo via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > Since this change what the expected post-rebase commit comment would look > like, related test expectations are adjusted to reflect the the new > expectation. A new test is added for the new expectation. Doesn't that mean automated tools people may have written require similar adjustment to continue working correctly if this change is applied? Can you tell us more about your expected use case? I am imagining that most people use the log messages from both/all commits being squashed when manually editing to perfect the final log message (as opposed to mechanically processing the concatenated message), so it shouldn't matter if the squash! title is untouched or commented out to them, and those (probably minority) who are mechanical processing will be hurt with this change, so I do not quite see the point of this patch. Thanks. > > Signed-off-by: Michael Rappazzo rappazzo@xxxxxxxxx [rappazzo@xxxxxxxxx] > > Michael Rappazzo (1): > sequencer: comment out the 'squash!' line > > sequencer.c | 1 + > t/t3404-rebase-interactive.sh | 4 +--- > t/t3415-rebase-autosquash.sh | 36 +++++++++++++++++++++++++++-------- > t/t3900-i18n-commit.sh | 4 ---- > 4 files changed, 30 insertions(+), 15 deletions(-) > > > base-commit: 8679ef24ed64018bb62170c43ce73e0261c0600a > Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-511%2Frappazzo%2Fcomment-squash-subject-line-v1 > Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-511/rappazzo/comment-squash-subject-line-v1 > Pull-Request: https://github.com/gitgitgadget/git/pull/511
