From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5745 invoked by alias); 8 Aug 2002 14:37:23 -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 5734 invoked from network); 8 Aug 2002 14:37:22 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 8 Aug 2002 14:37:22 -0000 Received: from dsl254-114-118.nyc1.dsl.speakeasy.net ([216.254.114.118] helo=nevyn.them.org ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17coPk-0006Wt-00; Thu, 08 Aug 2002 09:37:24 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17coQ2-0001Oo-00; Thu, 08 Aug 2002 10:37:42 -0400 Date: Thu, 08 Aug 2002 07:37:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: gdbserver/ChangeLog? Message-ID: <20020808143742.GA5362@nevyn.them.org> Mail-Followup-To: Andrew Cagney , gdb@sources.redhat.com References: <3D527C82.1040500@ges.redhat.com> <20020808141557.GA4426@nevyn.them.org> <3D527EB3.3020704@ges.redhat.com> <20020808142828.GA4893@nevyn.them.org> <3D528190.9080706@ges.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D528190.9080706@ges.redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-08/txt/msg00068.txt.bz2 On Thu, Aug 08, 2002 at 10:34:56AM -0400, Andrew Cagney wrote: > >On Thu, Aug 08, 2002 at 10:22:43AM -0400, Andrew Cagney wrote: > > > >>>On Thu, Aug 08, 2002 at 10:13:22AM -0400, Andrew Cagney wrote: > >>> > > > >>>>Daniel, > >>>> > >>>>Should there be a gdbserver/ChangeLog? I was recently doing some code > >>>>archology and was finding that the presence of gdbserver entries in > >>>>gdb/ChangeLog was making things mighty confusing. Often the same > >>>>function/variable appears but in a totally different context. > > > >>> > >>> > >>>Hmm, I think that's a good idea. Is it worth moving entries from the > >>>old ChangeLogs, or just starting a new one for future changes? > > > >> > >>The ``rewriting history'' problem. I don't know. > >> > >>I'm tempted with suggesting that entries in this years changelog being > >>moved but I don't know how independant they are. > > > > > >That sounds good to me. I'll give it a day or two and then move them > >over. > > Hmm, a better starting point would be date the last branch was cut > (which reminds me, the release process doesn't stamp the changelog when > that is done ...). Otherwize a diff of the changelogs between two > releases won't make much sense -> it will contain a lot of noise. Yeah, you're right. > The other more pragmatic aproach is to start it today, in 4 months, the > problem will go away anyway. There've been significant changes since the 5.2 release; I'd rather do it from there. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer