From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13143 invoked by alias); 13 Feb 2005 00:10:35 -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 13058 invoked from network); 13 Feb 2005 00:10:23 -0000 Received: from unknown (HELO mail.netspace.net.au) (203.10.110.71) by sourceware.org with SMTP; 13 Feb 2005 00:10:23 -0000 Received: from [192.168.1.11] (220-253-14-161.VIC.netspace.net.au [220.253.14.161]) by mail.netspace.net.au (Postfix) with ESMTP id 01C5343224; Sun, 13 Feb 2005 11:10:22 +1100 (EST) Message-ID: <420E9CBB.30003@netspace.net.au> Date: Sun, 13 Feb 2005 11:14:00 -0000 From: Russell Shaw User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1 MIME-Version: 1.0 To: Paul Schlie Cc: gdb@sources.redhat.com Subject: Re: Branching References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-02/txt/msg00096.txt.bz2 Paul Schlie wrote: >>Russell Shaw wrote: >>I made a new remote target for gdb that runs a hardware in-circuit >>emulator. I might add a software simulator target too. >> >>Is it usual to create a 'branch' of gdb for this? The files i >>work on are new ones that aren't a normal part of gdb. > > > Sounds interesting, but out of curiosity, why need a branch, as opposed > to aggregating target specific files into a configuration/ target-specific > directory, (just as arguably many of the target-specific files presently > scattered throughout gdb's source directory could/should also be)? I only followed the way things are currently done with files for other remote targets. The only reason for considering a branch is i thought maybe there was some standard way of accessing it from where ever gdb sources are currently hosted (i haven't done much cvs stuff). Section 15 of gdbint manual talks of branches: 15.4.1 Guidelines gdb permits the creation of branches, cut from the cvs repository, for experimental develop- ment. Branches make it possible for developers to share preliminary work, and maintainers to examine signicant new developments. The following are a set of guidelines for creating such branches: a branch has an owner... I was wondering if "experimental development" included adding new targets to gdb, without modifying the existing gdb files. Having an experimental branch could make it easier for one to check it out and work on it. The only other way i suppose is to keep the patches on sourceforge or somewhere?