From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27561 invoked by alias); 26 Apr 2005 03:58:56 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 27418 invoked from network); 26 Apr 2005 03:58:47 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org with SMTP; 26 Apr 2005 03:58:47 -0000 Received: from zaretski (IGLD-80-230-41-251.inter.net.il [80.230.41.251]) by legolas.inter.net.il (MOS 3.5.6-GR) with ESMTP id EFU28521 (AUTH halo1); Tue, 26 Apr 2005 06:56:55 +0300 (IDT) Date: Tue, 26 Apr 2005 03:58:00 -0000 From: "Eli Zaretskii" To: Mark Mitchell Message-ID: <01c54a13$Blat.v2.4$ee303d20@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 CC: me@cgf.cx, gdb-patches@sources.redhat.com, drow@false.org In-reply-to: <426D7B08.6010401@codesourcery.com> (message from Mark Mitchell on Mon, 25 Apr 2005 16:19:36 -0700) Subject: Re: PATCH: Support Windows in event-loop.c Reply-to: Eli Zaretskii References: <20050425145023.GD6543@trixie.casa.cgf.cx> <426D05D6.8010903@codesourcery.com> <20050425150422.GA13753@nevyn.them.org> <426D0A11.4060604@codesourcery.com> <20050425152324.GA15521@nevyn.them.org> <426D0C1D.8040600@codesourcery.com> <20050425153549.GA15967@nevyn.them.org> <426D5178.6010502@codesourcery.com> <01c549da$Blat.v2.4$626aed00@zahav.net.il> <426D6518.9050305@codesourcery.com> <20050425231507.GA21554@trixie.casa.cgf.cx> <426D7B08.6010401@codesourcery.com> X-SW-Source: 2005-04/txt/msg00338.txt.bz2 > Date: Mon, 25 Apr 2005 16:19:36 -0700 > From: Mark Mitchell > CC: gdb-patches@sources.redhat.com, drow@false.org, > Eli Zaretskii > > > Wow. That was fast. > > Sorry, did I misinterpret Eli's message? I took it as a commit > approval, but perhaps that was overly optimistic? You didn't misinterpret my message. However, since event-loop.c doesn't have a single responsible maintainer, it is generally advisable to wait for a few hours so that other maintainers could have an opportunity to comment on the patch.