public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom de Vries <tdevries@suse.de>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [committed][gdb/testsuite] Split up multi-exec test-cases
Date: Thu, 14 May 2020 18:14:27 +0100	[thread overview]
Message-ID: <47d9b44d-b7b1-7abc-034b-1e9381487beb@redhat.com> (raw)
In-Reply-To: <bb73b04d-e0d5-bc87-9243-ae7555ed41af@suse.de>

On 5/14/20 5:28 PM, Tom de Vries wrote:

> FWIW, I based this pattern on:
> ...
> $ ls -1  gdb/testsuite/gdb.base/all-architecture*
> gdb/testsuite/gdb.base/all-architectures-0.exp
> gdb/testsuite/gdb.base/all-architectures-1.exp
> gdb/testsuite/gdb.base/all-architectures-2.exp
> gdb/testsuite/gdb.base/all-architectures-3.exp
> gdb/testsuite/gdb.base/all-architectures-4.exp
> gdb/testsuite/gdb.base/all-architectures-5.exp
> gdb/testsuite/gdb.base/all-architectures-6.exp
> gdb/testsuite/gdb.base/all-architectures-7.exp
> gdb/testsuite/gdb.base/all-architectures.exp.in
> ...
> 
> I'm guessing .in was short for include.

Yeah, include or input.

> 
>> Could we just call these ".tcl" files?  If dejagnu would ignore those,
>> then that would work out great.
> 

No objection (with my the-one-who-added-all-architectures.exp.in originally hat).

Thanks,
Pedro Alves


  reply	other threads:[~2020-05-14 17:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 15:25 Tom de Vries
2020-05-14 15:32 ` Tom Tromey
2020-05-14 16:28   ` Tom de Vries
2020-05-14 17:14     ` Pedro Alves [this message]
2020-05-15 12:51     ` [committed][gdb/testsuite] Rename *.exp.in to *.exp.tcl Tom de Vries
2020-05-14 17:04 ` [committed][gdb/testsuite] Split up multi-exec test-cases Pedro Alves
2020-05-15 14:27   ` Tom de Vries
2020-05-18 14:13   ` Pedro Alves

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=47d9b44d-b7b1-7abc-034b-1e9381487beb@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).