From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25155 invoked by alias); 5 Dec 2014 10:05:43 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 25139 invoked by uid 89); 5 Dec 2014 10:05:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 05 Dec 2014 10:05:41 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 6CA49116425; Fri, 5 Dec 2014 05:05:39 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1ujFIdkMcHdJ; Fri, 5 Dec 2014 05:05:39 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id E4E2611641E; Fri, 5 Dec 2014 05:05:38 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id D70C346B66; Fri, 5 Dec 2014 14:05:35 +0400 (RET) Date: Fri, 05 Dec 2014 10:05:00 -0000 From: Joel Brobecker To: Pedro Alves Cc: Yao Qi , gdb-patches@sourceware.org Subject: Re: [PATCH] Don't enable gdbtk in testsuite Message-ID: <20141205100535.GG7899@adacore.com> References: <1416903049-30419-1-git-send-email-yao@codesourcery.com> <548094B1.8050708@redhat.com> <87y4qmd1qu.fsf@codesourcery.com> <548180B5.4060003@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <548180B5.4060003@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-12/txt/msg00124.txt.bz2 > Personally, I wouldn't be adverse to importing gdbtk into the official > gdb repo. I don't see how that could hurt -- we tend to worry > about insight anyway when we touch code that might affect it, like > most the deprecated_foo hooks. FWIW - I was hoping insight would be dead by now, but if people still use it and make updates, then I wouldn't be opposed either. The one thing to be careful of, I think, is handling of their commits. Probably just a third email list for insight-specific files? -- Joel