Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH] mi-var-cmd.exp, mi0-var-cmd.exp: accommodate gcc v3
Date: Sat, 09 Mar 2002 12:10:00 -0000	[thread overview]
Message-ID: <20020309151036.A27155@nevyn.them.org> (raw)
In-Reply-To: <3C8A6AC4.3020702@cygnus.com>

On Sat, Mar 09, 2002 at 03:04:20PM -0500, Andrew Cagney wrote:
> >On Sat, Mar 09, 2002 at 11:03:56AM -0600, Michael Elizabeth Chastain wrote:
> >
> >>Commited to gdb_5_2-branch.  I already committed to this to mainline.
> 
> >>Errr, in mainline, I added to the wrong ChangeLog.  I added to
> >>gdb/testsuite/ChangeLog instead of gdb/testsuite/gdb.mi/ChangeLog.
> >>Should I fix up the ChangeLog's in mainline, or add an entry
> >>to gdb/testsuite/gdb.mi/ChangeLog, or leave them alone?
> 
> I'd tweak it (just don't tell me :-).
> 
> >
> >Actually, I believe that gdb.mi/ChangeLog is obsolete.
> 
> ? I still use it and I see a few others do.

Last time I checked, which was some time ago, I got the impression you
were using the one in the toplevel testsuite/ dir instead.  We both
seem to have been a little inconsistent, me especially... which way
would you prefer it?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-03-09 20:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-09 22:02 Michael Elizabeth Chastain
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=20020309151036.A27155@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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