How to write git commit messages for submodule updates?

I always struggle to write good git commit messages for commits which did nothing except update which commit a submodule is on. What I really want to write is “just read the freaking submodule commit messages!”

Perhaps a slightly nicer solution is, does there exist something which goes to the submodule and concatenates all of the messages since the previous commit it was on in some nice fashion and automatically makes that the message?

  • Changing git commit message after push (given that no one pulled from remote)
  • Git: Best way to add only some parts of a file from another branch?
  • Git remove root commit
  • How do I visualise my git repo properly?
  • Why does `:Wq` in VIM cause my commit to fail later?
  • Move tag one commit ahead
  • git submodule for zxing (iPhone version)?
  • git subtree error “fatal: refusing to merge unrelated histories”
  • Rails deployment to staging using capistrano generates the following error
  • is it possible for git to track the “.git” folder?
  • Git: How do I rewind the Master branch on the remote origin
  • How to use Git for Unity3D source control?
  • One Solution collect form web for “How to write git commit messages for submodule updates?”

    I don’t know why this is weighing on you but I think there are probably only two basic reason you are going to update your submodules:

    1. You found a bug in the submodule and it was already fixed upstream. I this case just write:

      Update submodule XXX to vY.Z to add feature KKKK

      You probably also want to add additional detailed description about how this feature is impacting your repo, etc.

    2. You simply want to sync your submodules to the latest revs and don’t really care what was fixed or changed:

      Update submodule XXX to latest

    Git Baby is a git and github fan, let's start git clone.