[oe] [poky] Commit and Patch message guidelines - fifth draft
leon.woestenberg at gmail.com
Sun May 15 17:03:26 CEST 2011
On Thu, May 12, 2011 at 9:57 PM, Mark Hatle <mark.hatle at windriver.com> wrote:
> <...> Let the code
> tell the story of the mechanics of the change (as much as possible), and let
> your comment tell the other details -- i.e. what the problem was, how it
> manifested itself (symptoms), and if necessary, the justification for why the
> fix was done in manner that it was.
In other words, the long commit message must describe *why* the change
was needed (instead of what has changed).
I find this item the most lacking in current OpenEmbedded/Poky related commits.
Thanks for working on this,
More information about the Openembedded-devel