From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28407 invoked by alias); 4 Sep 2013 22:17:43 -0000 Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org Received: (qmail 28397 invoked by uid 89); 4 Sep 2013 22:17:43 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 04 Sep 2013 22:17:43 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.8 required=5.0 tests=BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r84MHeC1005195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 4 Sep 2013 18:17:40 -0400 Received: from valrhona.uglyboxes.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r84MHdvW008698 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 4 Sep 2013 18:17:40 -0400 Message-ID: <5227B183.2060702@redhat.com> Date: Wed, 04 Sep 2013 22:17:00 -0000 From: Keith Seitz User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Andrew Burgess CC: insight@sourceware.org Subject: Re: [PATCH] Remove use of deprecated_command_loop_hook References: <5215571A.3040403@broadcom.com> In-Reply-To: <5215571A.3040403@broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2013-q3/txt/msg00030.txt.bz2 Sorry for the delay on this: I've been out of the office for a bit. On 08/21/2013 05:11 PM, Andrew Burgess wrote: > I have commit access to gdb, but I have no idea if that extends to > gdb/gdbtk, and even if it did I obviously wouldn't commit without > approval :) I handle insight as an extension of gdb. Pretty much the same policies w.r.t. obvious patches, build errors, etc. If you have commit-after-approval on gdb, you do here, too. > What do you think? I actually wonder how something this simple has been overlooked for so long? Well, actually, I do know. Thank you for thinking about us! Please commit. Keith