[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43197.1239887097@turing-police.cc.vt.edu>
Date: Thu, 16 Apr 2009 09:04:57 -0400
From: Valdis.Kletnieks@...edu
To: David Miller <davem@...emloft.net>
Cc: torvalds@...ux-foundation.org, hpa@...or.com, mingo@...e.hu,
tglx@...utronix.de, rusty@...tcorp.com.au,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
davej@...hat.com
Subject: Re: Fix quilt merge error in acpi-cpufreq.c
On Wed, 15 Apr 2009 14:23:26 PDT, David Miller said:
> From: Linus Torvalds <torvalds@...ux-foundation.org>
> Date: Wed, 15 Apr 2009 12:43:02 -0700 (PDT)
>
> > And if it _is_ obvious, then the mechanical "Impact:" thing is pointless.
> >
> > In other words - in neither case does it actually help anything at all.
> > It's only distracting noise.
>
> FWIW I find the Impact: blurbs highly annoying too. Just freakin'
> say what the damn patch does in the commit message.
>
> If a person can't be bothered to skim the commit message text,
> this Impact: tag only gives them a false sense of understanding
> what the change does.
Maybe we can use it to flag security fixes, to appease the people complaining
they can't find the security fixes without reading the commit message text. ;)
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists