From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver/ChangeLog?
Date: Fri, 23 Aug 2002 12:56:00 -0000 [thread overview]
Message-ID: <20020823195649.GA26809@nevyn.them.org> (raw)
In-Reply-To: <3D5288B5.5080906@ges.redhat.com>
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
prev parent reply other threads:[~2002-08-23 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 7:13 gdbserver/ChangeLog? Andrew Cagney
2002-08-08 7:15 ` gdbserver/ChangeLog? Daniel Jacobowitz
2002-08-08 7:21 ` gdbserver/ChangeLog? William A. Gatliff
2002-08-08 7:22 ` gdbserver/ChangeLog? Andrew Cagney
2002-08-08 7:28 ` gdbserver/ChangeLog? Daniel Jacobowitz
2002-08-08 7:35 ` gdbserver/ChangeLog? Andrew Cagney
2002-08-08 7:37 ` gdbserver/ChangeLog? Daniel Jacobowitz
2002-08-08 8:05 ` gdbserver/ChangeLog? Andrew Cagney
2002-08-23 12:56 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020823195649.GA26809@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox