Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] unify objfile obstacks (4/4)
Date: Sat, 07 Feb 2004 02:05:00 -0000	[thread overview]
Message-ID: <20040207020544.50B874B364@berman.michael-chastain.com> (raw)

Hi Elena,

Could you please keep the old pattern in there too?

It makes my task easier, because I run the test suite from gdb HEAD
against gdb from gdb HEAD and gdb from gdb 6.0, and compare the two.
If you delete the old pattern then I get a false FAIL -> PASS
transition.

You can mark it:

  -expect "..." {
    # old gdb 6.0
    PASS ...
  }

So that it will get pruned eventually.

Michael C

===

2004-02-06  Elena Zannoni  <ezannoni@redhat.com>

        * gdb.base/maint.exp: Update test to reflect
         obstack changes.


             reply	other threads:[~2004-02-07  2:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07  2:05 Michael Elizabeth Chastain [this message]
2004-02-07 23:26 ` Elena Zannoni
  -- strict thread matches above, loose matches on Subject: below --
2004-02-08  2:30 Michael Elizabeth Chastain
2004-02-06 21:30 Elena Zannoni

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=20040207020544.50B874B364@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=ezannoni@redhat.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