From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8353 invoked by alias); 21 Sep 2004 10:33:20 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 8338 invoked from network); 21 Sep 2004 10:33:19 -0000 Received: from unknown (HELO smtp.uk.superh.com) (193.128.105.170) by sourceware.org with SMTP; 21 Sep 2004 10:33:19 -0000 Received: from sh-uk-ex01.uk.w2k.superh.com (sh-uk-ex01 [192.168.16.17]) by smtp.uk.superh.com (8.12.10/8.12.10) with ESMTP id i8LARBDJ011999; Tue, 21 Sep 2004 11:27:11 +0100 (BST) Received: from chloe.uk.w2k.superh.com ([192.168.17.40]) by sh-uk-ex01.uk.w2k.superh.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 21 Sep 2004 11:29:39 +0100 Received: (from renneckej@localhost) by chloe.uk.w2k.superh.com (8.11.6/8.11.6) id i8LAU8O29106; Tue, 21 Sep 2004 11:30:08 +0100 From: Joern Rennecke Message-Id: <200409211030.i8LAU8O29106@chloe.uk.w2k.superh.com> Subject: Re: SuperH patch contributions To: cagney@gnu.org (Andrew Cagney) Date: Tue, 21 Sep 2004 10:33:00 -0000 Cc: joern.rennecke@superh.com (Joern Rennecke), gdb@sources.redhat.com In-Reply-To: <414B2629.2030409@gnu.org> from "Andrew Cagney" at Sep 17, 2004 02:00:09 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Sep 2004 10:29:39.0795 (UTC) FILETIME=[E6833A30:01C49FC5] X-SW-Source: 2004-09/txt/msg00166.txt.bz2 > I'd recommend creating a branch so that you can both post and commit the > changes. Good luck! I had an accident, an now there is unfortunately not enough time left to do things nicely. I want to focus now on getting all the patches covered, and we can sort out later what part of it can be integrated and how. I got a 48 MB gzipped tar file of a sh64 gdb + simulator build. Uuencoded this is 66 MB. This is based on a March 2002 snapshot and a number of RedHat patches. I did mostly patches to the simulator to make it simulate the right thing. Some of the configury bits (which I didn't wrote) didn't work quite right (or maybe I was missing some undocumented incantation), so I had to patch some of the post-configuration files; this is why I included all the build files in the tarball and it is so large. It is too large for tha mailing list - or should I split it up into twenty messages? What is the preferred way to submit things that large? Note, there is no time left to identify the post-configuration mods or do patch review before I leave SuperH. The objective now is to make these tools available, and to get the copyright assignment to cover them (which depends on submitting the code).