From: Ben Elliston <bje@wasabisystems.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: DejaGnu 1.4.4 release
Date: Thu, 05 Feb 2004 20:38:00 -0000 [thread overview]
Message-ID: <87llnhb6sq.fsf@wasabisystems.com> (raw)
In-Reply-To: <40229AA6.4010005@gnu.org>
Hi Andrew
> - should src/dejagnu/ be replaced?
IMHO, yes. The 1.4.4 release is very close to the version in
src/dejagnu. I've since merged a handful of patches from src -> FSF
that were missed and I've a patch that can be applied after a 1.4.4
import that will ensure that nothing will be lost from src/dejagnu.
> - should src/dejagnu/ be removed?
What would the alternative be? To just expect (ha!) developers to
have DejaGnu installed on their systems?
I think as a first step, we should go with the former. After a bit of
time, we can consider removing it from src altogether.
Cheers, Ben
next prev parent reply other threads:[~2004-02-05 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 10:54 Ben Elliston
2004-02-05 19:34 ` Andrew Cagney
2004-02-05 20:38 ` Ben Elliston [this message]
2004-02-05 20:50 ` Gerald Pfeifer
2004-02-05 23:01 ` Joe Buck
2004-02-01 2:02 Michael Elizabeth Chastain
2004-02-05 23:21 Michael Elizabeth Chastain
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=87llnhb6sq.fsf@wasabisystems.com \
--to=bje@wasabisystems.com \
--cc=binutils@sources.redhat.com \
--cc=cagney@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@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