4 ms·
> it is generally left blank Not at all. > it adds no value It is used by Linus to check what's going on and see if there's anything he should check more clo
by bonzini 6y ago
> it is generally left blank
Not at all.
> it adds no value
It is used by Linus to check what's going on and see if there's anything he should check more closely (perhaps cross-checking the message with the diffstat); it is used by developers (now or in the future) and journalists to make themselves an idea of what is being merged; it may explain features that are in development and have preparatory work being merged; and so on.
So I'd say there's quite a bit of value there.
- quesera 6y agoEvery single one of those pieces of information is included in the original commit messages, which are included by incorporation. The merge commit message is the equivalent of forwarding an email to someone and adding your comment at the top: "Really interesting, read this!" "Hey, look what Joe said..." Or the ever-popular message in CEO-speak: "?" Rephrasing the committer's message in the merge commit would be redundant at best, and confusing at worst.