From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IXEeM-0006Dn-0Y for qemu-devel@nongnu.org; Mon, 17 Sep 2007 07:20:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IXEeK-0006Bx-UG for qemu-devel@nongnu.org; Mon, 17 Sep 2007 07:20:21 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IXEeK-0006Bh-Ps for qemu-devel@nongnu.org; Mon, 17 Sep 2007 07:20:20 -0400 Received: from owl.ecs.soton.ac.uk ([152.78.68.129]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IXEeK-0001sK-Ei for qemu-devel@nongnu.org; Mon, 17 Sep 2007 07:20:20 -0400 Received: from goose.ecs.soton.ac.uk (goose.ecs.soton.ac.uk [152.78.68.131]) by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l8HBK6ls020976 for ; Mon, 17 Sep 2007 12:20:06 +0100 Received: from [152.78.64.252] (panther [152.78.64.252]) (authenticated bits=0) by goose.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l8HBIub8022484 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 17 Sep 2007 12:18:56 +0100 Subject: Re: [Qemu-devel] qemu Changelog Makefile Makefile.target TODO ae... From: Philip Boulain In-Reply-To: References: <1190016521.14938.148.camel@rapid> <46d6db660709170127t415b3a06vbef6c5dd19cd172f@mail.gmail.com> <1190022138.14938.153.camel@rapid> Content-Type: text/plain Date: Mon, 17 Sep 2007 12:19:58 +0100 Message-Id: <1190027998.12960.3.camel@panther> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org > > > > DON'T DO THIS KIND OF COMMIT AGAIN, PLEASE. > > > if we were using git (but you can do it locally anyway), you would not > > > have these conflicts problems... > > Maybe... but Savannah uses a CVS frontend, as far as I know... > Those are excuses. So is a "you should have used X" argument. It doesn't invalidate the point that the commit was disruptive, and merely acts as bait for the grand old "version repository" flamewar.* > Like whitespace change is breaking your code. Really, I mean, come on. > Who do think you are kidding? Python programmers. ;) LionsPhil * See also, "if they'd used Perl instead of find/xargs/sed...".