From: Alexandre Oliva <aoliva@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Ben Elliston <bje+dated+1120509497.910ead@air.net.au>,
gdb-patches@sources.redhat.com
Subject: Re: PATCH Makefile.in
Date: Tue, 05 Jul 2005 17:33:00 -0000 [thread overview]
Message-ID: <or64vpdup3.fsf@livre.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20050704153539.GA22380@nevyn.them.org>
On Jul 4, 2005, Daniel Jacobowitz <drow@false.org> wrote:
> On Mon, Jul 04, 2005 at 10:46:35AM -0300, Alexandre Oliva wrote:
>> This is an argument for the removal of dejagnu and expect from the
>> tree, which I agree with. It's the one-line change in the test to
>> decide which RUNTEST to use that I'm opposing. I can't imagine such a
>> line is too much baggage to carry around. If you think so, well... I
>> guess I'll just shut up and wait until your next ports require changes
>> in dejagnu.
> I keep a local copy of dejagnu in my PATH. I've been doing this for
> years (and yes, I do deal with two ports that require changes in
> dejagnu). I find this way much more convenient...
But not as safe. E.g., I don't want net GCC test runs to be affected
by my local changes to dejagnu required by an ongoing port.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2005-07-05 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 20:38 Ben Elliston
2005-07-02 17:53 ` Alexandre Oliva
2005-07-03 19:06 ` Daniel Jacobowitz
2005-07-04 13:46 ` Alexandre Oliva
2005-07-04 15:35 ` Daniel Jacobowitz
2005-07-05 17:33 ` Alexandre Oliva [this message]
2005-07-05 17:48 ` Daniel Jacobowitz
2005-07-14 18:38 ` Alexandre Oliva
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=or64vpdup3.fsf@livre.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=bje+dated+1120509497.910ead@air.net.au \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.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