I would argue that: 1. If used on the "Git project itself" (as in my case), the commit message now cannot be used unedited because it is a conflict with the project's guidelines, and also conflicts with the format of "all" (or most) the other Git (and GitHub) commit titles. 2. If not "used on the Git project itself" (I assume it will always be used on A Git project), changing the commit title to be in line with the rest would not hurt anyone. Bjørn Erik 2017-08-04 23:21 GMT+02:00 Junio C Hamano <gitster@xxxxxxxxx>: > Bjørn Erik Pedersen <bjorn.erik.pedersen@xxxxxxxxx> writes: > >> I.e. "Squash 'somedir' changes" and not "Squashed ..." >> >> See >> >> https://github.com/git/git/blob/master/contrib/subtree/git-subtree.sh#L463 > > I do not think this is necessarily a good change. > > "git subtree" (in contrib/) is not a tool limited to be used on > projects that follow the same convention as the Git project itself.
