From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
Pedro Alves <palves@redhat.com>,
Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches <gdb-patches@sourceware.org>,
Yao Qi <qiyaoltc@gmail.com>
Subject: Re: [PATCH] Remove symlinks created in argv0-symlink.exp and general cleanup
Date: Wed, 12 Aug 2015 20:23:00 -0000 [thread overview]
Message-ID: <CADPb22RhTDh+Bq9BpinsbYm0DRERjx+J8GohvP=rNrDbUBQxkw@mail.gmail.com> (raw)
In-Reply-To: <20150812194137.GG22245@adacore.com>
On Wed, Aug 12, 2015 at 12:41 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> How often does it come up in the context of "make check"
>> (beyond the check-parallel implementation).
>> Other reasons for wanting to require GNU/Make are outside the scope
>> of my email. :-)
>
> That's true. But I think it's important to look at the complete picture
> while we're trying to decide the benefits vs downsides of switching over
> to GNU/Make. "make check" is one aspect that might benefit, but there
> are others, and it gives more weight, IMO, to the suggestion of making
> GNU/Make a requirement.
I think you'll find we're in agreement.
[who wouldn't be?]
prev parent reply other threads:[~2015-08-12 20:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 20:13 Simon Marchi
2015-08-03 14:23 ` Pedro Alves
2015-08-03 15:16 ` Simon Marchi
2015-08-03 16:34 ` Pedro Alves
2015-08-03 16:38 ` Pedro Alves
2015-08-03 18:10 ` Simon Marchi
2015-08-03 18:42 ` Pedro Alves
2015-08-04 16:11 ` Sergio Durigan Junior
2015-08-04 17:21 ` Joel Brobecker
2015-08-11 17:36 ` Doug Evans
2015-08-11 19:58 ` Joel Brobecker
2015-08-11 20:43 ` Doug Evans
2015-08-11 23:02 ` Joel Brobecker
2015-08-12 9:30 ` Pedro Alves
2015-08-12 16:40 ` Sergio Durigan Junior
2015-08-12 17:22 ` Joel Brobecker
2015-08-12 17:38 ` Doug Evans
2015-08-12 18:43 ` Joel Brobecker
2015-08-12 18:50 ` Doug Evans
2015-08-12 19:41 ` Joel Brobecker
2015-08-12 20:23 ` Doug Evans [this message]
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='CADPb22RhTDh+Bq9BpinsbYm0DRERjx+J8GohvP=rNrDbUBQxkw@mail.gmail.com' \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.com \
--cc=sergiodj@redhat.com \
--cc=simon.marchi@ericsson.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