4 ms·
OK, the commit messages are less ugly now, but they still give the wrong kind of information. Four lines of the commit message are about git-subrepo, which I d
by perlgeek 12y ago
OK, the commit messages are less ugly now, but they still give the wrong kind of information.
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.
- chocolateboy 12y agoThe metadata in the commit message isn't used in any way, so you can always: git commit --amend I personally find it a useful default, though, i.e. there's not usually much more I want to say than "added a subrepo: [metadata...]", and, for something like this, I'd rather err on the side of too much information than too little.