Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jimmy Guo <guo@cup.hp.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: Geoff Keating <geoffk@cygnus.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: recent dejagnu changes
Date: Mon, 07 Aug 2000 10:09:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.10008070947350.5575-100000@hpcll168.cup.hp.com> (raw)
In-Reply-To: <398C3E91.D0EDB934@cygnus.com>

I will submit a patch retaining the *dir_to_run change, and let Geoff try
it in GCC testing to make sure it works.

The solution to support both existing GCC and GDB test trees would be to
eliminate ${test_top_dirs} entries with common path prefix after
${srcdir} (keeping the parent only).  I will cook up a separate patch for
this.

- Jimmy

On Sat, 5 Aug 2000, Fernando Nasser wrote:

>Geoff Keating wrote:
>> 
>> > Actually, the dir_to_run and cmdline_dir_to_run change is OK ... that
>> > allows specification of a list of test suites, instead of one at a time.
>> 
>We do want to retain this functionality.
>
>> Could you post these as a separate patch, and test them separately?
>> They were committed together, and it's difficult to know which part
>> of the commit belongs with which change.
>> 
>Better than that would be if Jimmy submitted a patch commenting out (with the
>explanation why) the code that he believes is the offending one.  If that passes
>the gcc testsuite tests we commit it.
>
>I wonder if there isn't a way to accomodate both the gcc tree structure and the HP one...


       reply	other threads:[~2000-08-07 10:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <398C3E91.D0EDB934@cygnus.com>
2000-08-07 10:09 ` Jimmy Guo [this message]
2000-08-07 11:00   ` [RFA] dejagnu runtest.exp *dir_to_run Jimmy Guo
2000-08-07 11:34     ` [RFA] dejagnu runtest.exp redundant testing Jimmy Guo
2000-08-11 19:17       ` (withdraw) " Jimmy Guo
2000-08-14 11:02     ` [RFA] dejagnu runtest.exp *dir_to_run Jimmy Guo
     [not found] <Pine.LNX.4.10.10008080958530.12236-100000@hpcll168.cup.hp.com>
2000-08-08 11:29 ` recent dejagnu changes Geoff Keating
2000-08-08 12:52   ` Stan Shebs
2000-08-08 14:24     ` Geoff Keating
     [not found] <jmu2d0z0hb.fsf@envy.cygnus.com>
2000-08-04 23:40 ` Jimmy Guo
     [not found] <Pine.LNX.4.10.10008042223470.26402-100000@hpcll168.cup.hp.com>
2000-08-04 23:16 ` Geoff Keating
2000-08-04 20:31 Geoff Keating

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=Pine.LNX.4.10.10008070947350.5575-100000@hpcll168.cup.hp.com \
    --to=guo@cup.hp.com \
    --cc=fnasser@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=geoffk@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