From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16851 invoked by alias); 12 Feb 2005 19:57:18 -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 16843 invoked from network); 12 Feb 2005 19:57:15 -0000 Received: from unknown (HELO sccrmhc12.comcast.net) (204.127.202.56) by sourceware.org with SMTP; 12 Feb 2005 19:57:15 -0000 Received: from [10.0.1.3] (h000393256f12.ne.client2.attbi.com[24.61.199.96]) by comcast.net (sccrmhc12) with SMTP id <2005021219571301200qc2s1e>; Sat, 12 Feb 2005 19:57:14 +0000 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Sun, 13 Feb 2005 00:10:00 -0000 Subject: Re: Branching From: Paul Schlie To: Russell Shaw CC: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-SW-Source: 2005-02/txt/msg00095.txt.bz2 > 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)?