On Wed, Sep 16, 2015 at 10:06:56AM +0800, Yuanhan Liu wrote: > If not, I'd like to put them into the commit log, as putting it > outside the commit log gives unnecessary extra burden to patch > author when he need update several version change information > in a patch set: he has to format the patch set first, and add > them one by one by editing those patches.
I personally just describe the changes in the cover letter. In fact, while not a lot of people do this, git-backport-diff (from https://github.com/codyprime/git-scripts.git) is a handy tool to show which patches changed since the previous version, and it only works if the change log is in the cover letter. Or you can stick --- in the commit log as you have found out - but that depends on the patch author being careful to log all edits. -- MST
