From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IXBuG-0001Ov-1W
	for qemu-devel@nongnu.org; Mon, 17 Sep 2007 04:24:36 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IXBuF-0001Oc-KB
	for qemu-devel@nongnu.org; Mon, 17 Sep 2007 04:24:35 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IXBuF-0001OU-3g
	for qemu-devel@nongnu.org; Mon, 17 Sep 2007 04:24:35 -0400
Received: from rv-out-0910.google.com ([209.85.198.186])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <christian.michon@gmail.com>) id 1IXBuE-0003Z2-PD
	for qemu-devel@nongnu.org; Mon, 17 Sep 2007 04:24:34 -0400
Received: by rv-out-0910.google.com with SMTP id g11so4796822rvb
	for <qemu-devel@nongnu.org>; Mon, 17 Sep 2007 01:24:33 -0700 (PDT)
Message-ID: <46d6db660709170124keafa633ocbbd0c2533304f83@mail.gmail.com>
Date: Mon, 17 Sep 2007 10:24:32 +0200
From: "Christian MICHON" <christian.michon@gmail.com>
Subject: Re: [Qemu-devel] qemu Changelog aes.c arm-dis.c arm-semi.c block...
In-Reply-To: <E1IXBg3-0003Tb-1d@cvs.savannah.gnu.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E1IXBg3-0003Tb-1d@cvs.savannah.gnu.org>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On 9/17/07, Thiemo Seufer <ths@networkno.de> wrote:
> Log message:
>         find -type f | xargs sed -i 's/[\t ]*$//g' # Yes, again. Note the star in the regex.

so you're going to do this each time you receive a faulty patch ?
I thought this kind of search and replace is more likely to happen
when cleaning up just before release.

is qemu-0.9.1 going to be reached anytime soon then ?

;-)

-- 
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !