Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@cygnus.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: Fernando Nasser <fnasser@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] New tests for 'const' and 'volatile' expressions
Date: Mon, 03 Dec 2001 10:58:00 -0000	[thread overview]
Message-ID: <3C0BCB8F.C2BF7925@cygnus.com> (raw)
In-Reply-To: <3BF3E676.FE6A59C3@redhat.com>

Fernando Nasser wrote:
> 
> Michael Snyder wrote:
> >
> > Fernando Nasser wrote:
> > >
> > > Michael Snyder wrote:
> > > >
> > > > This is a test that I forgot to submit back in September,
> > > > after submitting the changes to the expression parser that
> > > > permitted more complex expressions involving const and volatile.
> > >
> > > Nice, new tests are good!
> > >
> > > > I've tested the test on several native and embedded targets.
> > > >
> > >
> > > Do they pass?
> >
> > Oh, yes -- no failures, when tested on the main branch.
> > I have not tested the 5.1 branch.  If it fails, there would
> > be two choices:
> >
> >   * merge the parser patch onto the branch
> >   * omit this test from the branch.
> > >
> 
> As this is a new feature, it would not make much sense have it
> where the feature was not yet added, right?
> 
> So I would say it goes where you previous patch goes, and only there.
> 
> I guess you can check it in to the trunk now.

Committed.


  reply	other threads:[~2001-12-03 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-04 20:11 Michael Snyder
2001-11-05 15:00 ` Fernando Nasser
2001-11-05 15:26   ` Michael Snyder
2001-11-06 10:18     ` Fernando Nasser
2001-12-03 10:58       ` Michael Snyder [this message]
2001-11-04 20:31 Michael Elizabeth Chastain
2001-11-05 15:04 ` Fernando Nasser
2001-11-05 22:43 Michael Elizabeth Chastain
2001-11-06  9:46 ` Fernando Nasser

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=3C0BCB8F.C2BF7925@cygnus.com \
    --to=msnyder@cygnus.com \
    --cc=fnasser@cygnus.com \
    --cc=fnasser@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