[PATCH] Add support of the 'mmc.type' parameter

[Danny Kukawka]

On Dienstag, 26. Februar 2008, Dan Nicholson wrote:
> On Tue, Feb 26, 2008 at 12:11 AM, Andy Shevchenko <andy at smile.org.ua> wrote:
> >  P.S. Please, direct me how to add description in the git? Do I need to
> > past different paragraphs for subject and description parts?
>
> That's typically what people do when there is more than a trivial change.

Or simply take a look into the HACKING file in HAL source:

Committing code
===

 - Commit messages should be of the form (the five lines between the
   lines starting with ===)

=== begin example commit ===
short explanation of the commit

Longer explanation explaining exactly what's changed, whether any
external or private interfaces changed, what bugs were fixed (with bug
tracker reference if applicable) and so forth. Be concise but not too brief.
=== end example commit ===

 - Always add a brief description of the commit to the _first_ line of
   the commit and terminate by two newlines (it will work without the
   second newline, but that is not nice for the interfaces).

 - First line (the brief description) must only be one sentence and
   must not start with a capital letter. Don't use a trailing period
   either.

 - The main description (the body) is normal prose and should use normal
   punctuation and capital letters where appropriate. Normally, for patches
   sent to a mailing list it's copied from there.

 - When committing code on behalf of others use the --author option, e.g.
   git commit -a --author "Joe Coder <joe at coder.org>"


Danny