From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25789 invoked by alias); 4 May 2006 15:04:18 -0000 Received: (qmail 25781 invoked by uid 22791); 4 May 2006 15:04:18 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 04 May 2006 15:04:16 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FbfNG-0000Jp-H6; Thu, 04 May 2006 11:04:14 -0400 Date: Thu, 04 May 2006 15:04:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: gdb@sources.redhat.com Subject: Re: RFC: MI output during program execution Message-ID: <20060504150414.GE32605@nevyn.them.org> Mail-Followup-To: Nick Roberts , gdb@sources.redhat.com References: <17458.60694.135878.624750@farnswood.snap.net.nz> <20060404220637.GA12064@nevyn.them.org> <17486.36188.127822.347550@farnswood.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17486.36188.127822.347550@farnswood.snap.net.nz> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00024.txt.bz2 On Wed, Apr 26, 2006 at 08:58:04AM +1200, Nick Roberts wrote: > 1) Create a branchpoint of current HEAD for gdb+dejagnu: > > cvs rtag nickrob-200604026-branchpoint gdb+dejagnu Right. You can just use the gdb module nowadays; the only difference is that gdb+dejagnu will include tcl by accident. Expect and DejaGNU aren't in the tree any more. Could I persuade you to update the manual? > 2) Create a branch from that branchpoint: > > cvs rtag -b -r nickrob-200604026-branchpoint nickrob-200604026-branch \ > gdb+dejagnu Right. > 3) Update my working directory to that branch: > > cvs update -r nickrob-200604026-branch Right. > 4) Add files called ChangeLog-async, README-async, TODO-async. Right. I recommend putting these under the gdb subdirectory; otherwise there's some trouble getting CVS to check them out by default because of how we use modules. > 5) Modify version.in appropriately. Sure, if you want to clearly identify the branch - always a good idea. > 5) Commit my/Apple's changes. Right. > 6) Post those changes to gdb-patches. Right. > 7) Do regular merges with trunk: > > cvs update -j HEAD (?) Well, it's more complicated than this. You need tags at mergepoints - see the last bit of the chapter which mentions cvs up -j. It's a bit of a pain. > When I've got this far I'll also explain what the code does and what I would > like it to do in the future (from README-async) on the gdb mailing list. Great! Your steps look fine; feel free. -- Daniel Jacobowitz CodeSourcery