From: Thomas Koenig <tkoenig@netcologne.de>
To: Mikael Morin <mikael.morin@sfr.fr>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran] Simplify lbound
Date: Sun, 03 May 2015 20:38:00 -0000 [thread overview]
Message-ID: <5546872F.7040507@netcologne.de> (raw)
In-Reply-To: <5543EA34.6060304@sfr.fr>
Hi Mikael,
Looks good.
In general, it is better to restrict changes to existing test cases to
the necessary minimum that they still pass, and add new code to new
test cases. This makes regressions easier to track.
So, OK with that change.
Thomas
next prev parent reply other threads:[~2015-05-03 20:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 11:34 Thomas Koenig
2015-04-25 18:13 ` Mikael Morin
2015-04-27 18:45 ` Thomas Koenig
2015-04-27 19:22 ` Thomas Koenig
2015-04-30 18:46 ` Mikael Morin
2015-05-01 21:04 ` Mikael Morin
2015-05-03 20:38 ` Thomas Koenig [this message]
2015-05-10 13:59 ` Mikael Morin
2015-05-10 20:43 ` H.J. Lu
2015-05-10 22:08 ` Thomas Koenig
2015-05-11 13:17 ` Mikael Morin
2015-05-12 7:08 ` Thomas Koenig
2015-05-12 10:04 ` Mikael Morin
2015-05-02 10:50 ` H.J. Lu
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=5546872F.7040507@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikael.morin@sfr.fr \
/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).