From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21250 invoked by alias); 23 Aug 2002 19:56:04 -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 21243 invoked from network); 23 Aug 2002 19:56:03 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 23 Aug 2002 19:56:03 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17iKXO-0001vS-00; Fri, 23 Aug 2002 14:56:06 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17iKY5-0007g0-00; Fri, 23 Aug 2002 15:56:49 -0400 Date: Fri, 23 Aug 2002 12:56:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: gdbserver/ChangeLog? Message-ID: <20020823195649.GA26809@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> <20020808143742.GA5362@nevyn.them.org> <3D5288B5.5080906@ges.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D5288B5.5080906@ges.redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-08/txt/msg00305.txt.bz2 On Thu, Aug 08, 2002 at 11:05:25AM -0400, Andrew Cagney wrote: > >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. > > M'kay by me. Done now. Future changes to gdbserver/ should go in gdbserver/ChangeLog. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer