From: Fernando Nasser <fnasser@redhat.com>
To: Rob Savoye <rob@welcomehome.org>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
bug-dejagnu@gnu.org
Subject: Re: [Bug-dejagnu] Dejagnu and parallel make tests of gcc
Date: Wed, 25 Sep 2002 08:49:00 -0000 [thread overview]
Message-ID: <3D91DB00.20005@redhat.com> (raw)
In-Reply-To: <20020924104439.C8038@welcomehome.org>
Rob Savoye wrote:> On Tue, Sep 24, 2002 at 05:14:02PM +0100, Richard Earnshaw wrote:
>
>
>>Ok, first question. Is the copy of dejagnu on sources.redhat.com (the one
>>in gdb) the master copy these days, or is there some other mailing list
>>for dejagnu framework patches?
>
>
> The official sources are on Savannah. www.gnu.org/software/dejagnu should
> get you there. I do believe sources.redhat.com has recently been synced up
> with the master repository at the FSF. But these two repositories are usually
> reasonably close to each other.
>
Yes, except for one baseboard file and configuration they are the same
(some blank lines and space differences which I will get rid of after Rob
finishes with the dejagnu release).
>
>> The second patch is to the dejagnu framework itself and ensures that when
>>we transfer the object to the (potentially remote) host we use a filename
>>that will not conflict with any other -- in this case I've chosen
>>${tool}_tg.o, which should be fairly safe.
>
>
> Looks safe to me. I'll check it in after the DejaGnu 1.4.3 release
> happens over the next day or so. (I hope) I'm just trying to get my
> release files uploaded to the FSF still... then it's done.
>
It is OK with me as well. Please check it in sources.redhat.com
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2002-09-25 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200209241614.g8OGE2030397@pc960.cambridge.arm.com>
2002-09-24 9:49 ` Rob Savoye
2002-09-25 8:49 ` Fernando Nasser [this message]
2002-09-25 9:16 ` Rob Savoye
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=3D91DB00.20005@redhat.com \
--to=fnasser@redhat.com \
--cc=bug-dejagnu@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=rob@welcomehome.org \
/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