This was fixed recently. [1]
> I haven't tried subtree yet, will do that next :-)
The git-subrepo intro has a pretty good overview of the issues with git-subtree. [2]
[1] https://github.com/ingydotnet/git-subrepo/issues/40
[2] https://github.com/ingydotnet/git-subrepo/blob/master/Intro....
Four lines of the commit message are about git-subrepo, which I don't care about. I'm not a git-subrepo developer, and don't care what version of the tool was used to generate the commit.
What I do care a lot about is why a commit was made, and those auto-generated commit messages don't tell me that at all. They can't, because the tools don't read minds. That's why git usually prompts me for a commit message. I like that. It's one of the reasons I'm using version control. It would be nice if git-subrepo played along.
git commit --amend