From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IXHVo-0001wY-NI
	for qemu-devel@nongnu.org; Mon, 17 Sep 2007 10:23:44 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IXHVn-0001vW-53
	for qemu-devel@nongnu.org; Mon, 17 Sep 2007 10:23:44 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IXHVm-0001vS-Sd
	for qemu-devel@nongnu.org; Mon, 17 Sep 2007 10:23:42 -0400
Received: from phoenix.bawue.net ([193.7.176.60] helo=mail.bawue.net)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <ths@networkno.de>) id 1IXHVm-0004mu-N7
	for qemu-devel@nongnu.org; Mon, 17 Sep 2007 10:23:42 -0400
Date: Mon, 17 Sep 2007 14:46:08 +0100
From: Thiemo Seufer <ths@networkno.de>
Subject: Re: [Qemu-devel] qemu Changelog aes.c arm-dis.c arm-semi.c block...
Message-ID: <20070917134607.GC9972@networkno.de>
References: <E1IXBg3-0003Tb-1d@cvs.savannah.gnu.org>
	<46d6db660709170124keafa633ocbbd0c2533304f83@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46d6db660709170124keafa633ocbbd0c2533304f83@mail.gmail.com>
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: Christian MICHON <christian.michon@gmail.com>
Cc: qemu-devel@nongnu.org

Christian MICHON wrote:
> 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 did so for some months now.

> I thought this kind of search and replace is more likely to happen
> when cleaning up just before release.

It is supposed to happen only once.
It was twice now, because I made a mistake.


Thiemo