From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: binutils@sources.redhat.com, cagney@gnu.org, gcc@gcc.gnu.org,
gdb@sources.redhat.com
Cc: bje@wasabisystems.com
Subject: Re: DejaGnu 1.4.4 release
Date: Thu, 05 Feb 2004 23:21:00 -0000 [thread overview]
Message-ID: <20040205232152.EDEA84B364@berman.michael-chastain.com> (raw)
Andrew asks the key questions:
> - should src/dejagnu/ be replaced?
> - should src/dejagnu/ be removed?
My opinion:
Go for removal first. Tell people that the sourceware versions of
Expect and Dejagnu are going away and they need to use the upstream
versions. Provide doco for downloading and building Tcl+Expect+Dejagnu.
(I can do that part).
Wait a month. If no one objects, then kill the sourceware versions
of Expect and Dejagnu.
Michael C
next reply other threads:[~2004-02-05 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 23:21 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-01 2:02 Michael Elizabeth Chastain
2004-01-30 10:54 Ben Elliston
2004-02-05 19:34 ` Andrew Cagney
2004-02-05 20:38 ` Ben Elliston
2004-02-05 20:50 ` Gerald Pfeifer
2004-02-05 23:01 ` Joe Buck
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=20040205232152.EDEA84B364@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=binutils@sources.redhat.com \
--cc=bje@wasabisystems.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