Ian Romanick <[email protected]> writes: > From: Ian Romanick <[email protected]> > > Signed-off-by: Ian Romanick <[email protected]> > ---
I really prefer not to see commits with only the single-line summary for
a commit message.
The single-line summary is perfect for describing "what" the patch
does. And the above is a great example.
The rest of the commit message should describe "why" the patch is doing
what it does. And whenever it's missing, I'm left wondering.
Here, for example, you start tracking the packing mode. But nothing is
actually using the tracked information. I can guess that you are laying
the groundwork for something later. But the commit message should say
that and tell me what it is. That can help a lot for patch review.
It could even be something really short such as:
We'll need this later for the Frobbenheim pass.
And similar for later patches in the series.
-Carl (who might be stepping on some toes, culturally-speaking)
pgproYEroy_o_.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-dev
