Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@cygnus.com, drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] mi-var-cmd.exp, mi0-var-cmd.exp: accommodate gcc v3
Date: Sat, 09 Mar 2002 22:02:00 -0000	[thread overview]
Message-ID: <200203100602.g2A622l00964@duracef.shout.net> (raw)

I'm allergic to removing information from ChangeLogs, but I feel
comfortable adding a duplicate entry to gdb.mi/ChangeLog.  I don't
think a future historian would get too confused by that.

So that's what I'll do.  And in the future, I'll remember that
gdb.mi/ChangeLog exists, and use it (it looks like it's still active).

If only that were the worst problem gdb had.

Michael C


             reply	other threads:[~2002-03-10  6:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09 22:02 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-09  9:04 Michael Elizabeth Chastain
2002-03-09  9:07 ` Daniel Jacobowitz
2002-03-09 12:04   ` Andrew Cagney
2002-03-09 12:10     ` Daniel Jacobowitz
2002-03-05 11:50 Michael Elizabeth Chastain
2002-03-05 11:41 Michael Elizabeth Chastain

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=200203100602.g2A622l00964@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@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