Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver/ChangeLog?
Date: Thu, 08 Aug 2002 07:37:00 -0000	[thread overview]
Message-ID: <20020808143742.GA5362@nevyn.them.org> (raw)
In-Reply-To: <3D528190.9080706@ges.redhat.com>

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


  reply	other threads:[~2002-08-08 14:37 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         ` Daniel Jacobowitz [this message]
2002-08-08  8:05           ` gdbserver/ChangeLog? Andrew Cagney
2002-08-23 12:56             ` gdbserver/ChangeLog? Daniel Jacobowitz

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=20020808143742.GA5362@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