Am Freitag, 23. November 2012, 16:55:21 schrieb Heiko Voigt:
> I am still a little bit undecided about an automatically crafted commit.
> At $dayjob we sometimes update submodules to their tip without any
> superproject changes just to make sure we use the newest version. Most
> of the time the commit messages are along the lines of "updated
> submodule x to master".
> On one hand Junio is right that the person updating to the newest
> submodule stuff has no clue what to write in this message.
I've been thinking about that for a while, when I started using submodules. In
the end, I concluded, that what I really want to see in the commit message, is
something similar to $(git shortlog $OLD_SHA1..$NEW_SHA1).
I've scripted that and taught my CI-Server to do it automatically, if
possible. So most of the time, I really don't want an "automatically crafted
commit" whenever something causes the tip of a submodule to be at a new SHA1.
Just my $.02, though.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html