Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: msnyder@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] gdb.base/callfuncs.exp: make all test names unique
Date: Wed, 23 May 2001 11:20:00 -0000	[thread overview]
Message-ID: <3B0BFEE3.14B7400F@redhat.com> (raw)
In-Reply-To: <200105231816.LAA13966@bosch.cygnus.com>

Michael Elizabeth Chastain wrote:
> 
> chastain> ! gdb_test "next" "t_double_values\\(double_val1, double_val2\\);.*" "next 1"
> chastain> ! gdb_test "next" "t_structs_c\\(struct_val1\\);.*" "next 2"
> 
> snyder> I wonder if it would not be preferable to use "next over t_double_values"
> snyder> and "next over t_structs_c".
> 
> nasser> Michael (Chastain), please check it in your patch with these changes.
> nasser> Thank you very much to help eliminating these ambiguities.
> 
> Oops, actually that should be "next to t_double_values" rather than
> "next over t_double_values" and so on.  It still looks better than
> "next" or "next 1".
> 
> Works for me, I will use "next to t_double_values" and check it in.
> 

Thanks again.

Cheers,
Fernando

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


       reply	other threads:[~2001-05-23 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200105231816.LAA13966@bosch.cygnus.com>
2001-05-23 11:20 ` Fernando Nasser [this message]
2001-05-23 12:15 Michael Elizabeth Chastain
2001-05-23 15:19 ` Fernando Nasser
  -- strict thread matches above, loose matches on Subject: below --
2001-05-21 11:12 Michael Elizabeth Chastain
2001-05-20  5:03 Michael Elizabeth Chastain
2001-05-21 10:52 ` Michael Snyder
2001-05-23  9:40   ` 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=3B0BFEE3.14B7400F@redhat.com \
    --to=fnasser@redhat.com \
    --cc=chastain@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.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