From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5613 invoked by alias); 5 Aug 2007 06:55:37 -0000 Received: (qmail 5427 invoked by uid 22791); 5 Aug 2007 06:55:36 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 05 Aug 2007 06:55:34 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 124AE2A9C17; Sun, 5 Aug 2007 02:55:33 -0400 (EDT) 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 nZOzLyoBqU3u; Sun, 5 Aug 2007 02:55:33 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id D02262A9C12; Sun, 5 Aug 2007 02:55:32 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 0BF26E7B54; Sat, 4 Aug 2007 23:58:57 -0700 (PDT) Date: Sun, 05 Aug 2007 06:55:00 -0000 From: Joel Brobecker To: Markus Deuling Cc: GDB Patches , Ulrich Weigand Subject: Re: [rfc] [00/12] Get rid of current_gdbarch Message-ID: <20070805065857.GA11351@adacore.com> References: <46B31B13.4020304@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46B31B13.4020304@de.ibm.com> User-Agent: Mutt/1.4.2.2i 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 X-SW-Source: 2007-08/txt/msg00107.txt.bz2 > Some later patches will be non-trivial and hard for me to test due to lack > of those machines. It would be great if some of you could test patches for > different archs like mips, arm, etc. but this will still take a while. I can help with some of the testing, as usual. But I'm a bit nervous, and I think it would be nice to branch off gdb-6.7 before applying these particular trickier changes. The only thing that is holding me up is the change of licensing in the source headers. I was kinda hoping that the well known "someone" would take care of it while I'm on holiday, but I might have to jump in and help with the effort. I really want to see gdb-6.7 out soon! In the meantime, I propose to hold the tricky patches until the gdb-6.7 branch is created. Would that be ok? -- Joel