> BTW, can you use more consistent changeset messages? I always
> at least allude to what is being changed, for example I changed
> all of your messages to be of the form:
>
> [ATM]: Blah blah blah in HE driver.
>
> This tells the reader that:
>
> 1) It's an ATM change.
> 2) It's to the HE driver.
> 3) The change made was "Blah blah blah" :-)
I'd also add...
4) keep the first line a brief oneliner summary, as it
gets truncated when Linus generates the shortlog.
A number of people (self included) have adopted this
impromptu 'standard' for bk comments. Maybe it should
get documented in Documentation/BK-usage/bk-kernel-howto.txt
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/