merges

[Joern RENNECKE]

Jakub Jelinek wrote:

>  
>
>Yes.  I think they are useful for all branches if you backport a patch for
>a particular fix or e.g. fix something that is not yet fixed on the trunk
>and will be only when a particular devel branch with that fix is merged
>into trunk.  But in all cases that should be a single commit to fix a
>particular bug (or a set of closely related bugs).  Plain merges from
>other branches should just say what branch, perhaps revisions were merged.
>  
>
I agree.  Long log messages might be useful for a revision, but not for 
all the bugs affected -
if the commit message is larger than xxx bytes, the bugs should get a 
message from a short
template with the revision(s) involved and a link to the commit message 
filled in.