Re: [PATCH] Documentation: Add "how to write a good patch summary"to SubmittingPatches

[Linus Torvalds]

On Thu, 16 Apr 2009, Theodore Tso wrote:

> On Thu, Apr 16, 2009 at 10:12:55PM +0200, Ingo Molnar wrote:
> > as a bug triager i can, within 1 minute, sort all the commits by 
> > risk:
> > 
> > Low risk cleanups:
> >     ...
> > Runtime crash fixes:
> >     ...
> > Robustness enhancements:
> >     ...
> > Low-risk features:
> >     ...
> > High-risk features:
> >     ...
> 
> Sure, but if that's the goal, maybe instead we should have some
> keywords that we tag onto one-line summary, i.e.
> 
> ext4 <LR,cleanup>: 

Hell no.

The fact is, those "low risk cleanups" break things.

People who think that you can assess the risk of a commit before-hand and 
then rely on it are clueless morons.

Stop doing this. If we're just talking about some machine-readable pattern 
matching, JUST DON'T DO IT. It's going to be wrong. It's going to be wrong 
because people don't do it right, but it's going to be wrong because even 
when people _do_ mark everything right, they'll still be wrong.

Write English. Don't maek some idiotic commit markers that will make 
things harder to read AND WILL BE WRONG.

			Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/