From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13842 invoked by alias); 12 Aug 2003 22:01:55 -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 13835 invoked from network); 12 Aug 2003 22:01:54 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 12 Aug 2003 22:01:54 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h7CM1st14893 for ; Tue, 12 Aug 2003 18:01:54 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h7CM1nL15007; Tue, 12 Aug 2003 18:01:49 -0400 Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id h7CM1mO08184; Tue, 12 Aug 2003 15:01:48 -0700 Message-ID: <3F3963CC.5070300@redhat.com> Date: Tue, 12 Aug 2003 22:01:00 -0000 From: Michael Snyder User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nick Clifton CC: Ben Elliston , gdb-patches@sources.redhat.com Subject: Re: DejaGnu merge References: <87znif8p81.fsf@sashimi.wasabisystems.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-08/txt/msg00210.txt.bz2 Nick Clifton wrote: >Hi Ben, > > > >>I would like to attempt to merge the FSF DejaGnu tree >> >> > >I assume that you mean the master sources on Savannah ? > > > >>into the sources.redhat.com "son of devo" tree. Any objections or >>forseen hiccups? I will gladly post a patch for approval >>beforehand. >> >> > >The most important thing will be to make sure that the test harness >still works after the merge. Please could you try several different >kinds of before/after tests to make sure nothing breaks. Off the top >of my head I would suggest running the gcc, g++, gdb, ld, binutils and >gas testsuites for and x86 native, a cygwin native, a cross-compiler >using a simulator to run the built binaries and a cross-compiler with >the binaries running on a remote target board. > And maybe a sim/testsuite test.