From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39355) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvUKZ-0001lL-74 for qemu-devel@nongnu.org; Thu, 09 Feb 2012 08:46:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RvUKU-0002Z5-3E for qemu-devel@nongnu.org; Thu, 09 Feb 2012 08:46:35 -0500 Received: from mail-pw0-f45.google.com ([209.85.160.45]:50010) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvUKT-0002Ys-T2 for qemu-devel@nongnu.org; Thu, 09 Feb 2012 08:46:30 -0500 Received: by pbbro12 with SMTP id ro12so1753079pbb.4 for ; Thu, 09 Feb 2012 05:46:28 -0800 (PST) Message-ID: <4F33CE30.1040706@codemonkey.ws> Date: Thu, 09 Feb 2012 07:46:24 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <4F324A60.7070600@samsung.com> <4F326D66.6060808@suse.de> <4F329385.4030203@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Restore consistent formatting List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: Blue Swirl , =?ISO-8859-1?Q?Andreas_F=E4r?= =?ISO-8859-1?Q?ber?= , qemu-devel@nongnu.org, Evgeny Voevodin , Dmitry Solodkiy On 02/09/2012 03:48 AM, Markus Armbruster wrote: > Anthony Liguori writes: > >> On 02/08/2012 09:04 AM, malc wrote: >>> On Wed, 8 Feb 2012, Andreas F?rber wrote: >>> >>>> malc, >>>> >>>> Arbitrarily reformatting your files is not okay. If you want a different >>>> formatting, you need to fix checkpatch.pl first to not error on that >>>> formatting in your files. >>> >>> It was always formatter like this (internally consistent), then others >>> added code which made it not so. >> >> We do have a mixed style in the audio layer. I'm not happy about that >> but I also feel strongly that going through and doing a reformat is >> not a worthwhile exercise. >> >> I can also understand the desire to keep things consistent. But >> patches should always go to the mailing list. I certainly would have >> acked such a patch FWIW. > > You buried the one truly important sentence, let me dig it out for you: > > *** Patches should always go to the mailing list *** > > Exceptions need justification. Responsible handling embargoed security > issues may qualify. Style fixes certainly not. 100% agreed. Regards, Anthony Liguori > > [...] >