From: Mike Stump <mikestump@comcast.net>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: [RFC] Dejagnu patch to handle multi-line directives
Date: Mon, 12 Jun 2017 16:58:00 -0000 [thread overview]
Message-ID: <63D22825-6B8C-4C83-9135-877F47A7BD2A@comcast.net> (raw)
In-Reply-To: <b096fda2-5ed8-f8c1-ddd0-4ee1bb7f8565@mentor.com>
On Jun 10, 2017, at 12:57 AM, Tom de Vries <Tom_deVries@mentor.com> wrote:
>
> one thing that has bothered me on a regular basis is the inability to spread long dejagnu directives over multiple lines.
I'm not terribly in favor of this. I'd like to retain the ability to grep and sed single line things. It makes exploring and finding things easier. Also, if we bulk convert to a new framework system for running test cases, the conversion is easier.
next prev parent reply other threads:[~2017-06-12 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 7:57 Tom de Vries
2017-06-10 8:03 ` Tom de Vries
2017-06-11 0:42 ` Segher Boessenkool
2017-06-12 7:59 ` Richard Sandiford
2017-06-12 18:54 ` Pedro Alves
2017-06-13 6:59 ` Richard Sandiford
2017-06-12 16:58 ` Mike Stump [this message]
2017-06-20 13:28 ` Rainer Orth
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=63D22825-6B8C-4C83-9135-877F47A7BD2A@comcast.net \
--to=mikestump@comcast.net \
--cc=Tom_deVries@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).