From: Alexandre Oliva <aoliva@redhat.com>
To: Ben Elliston <bje+dated+1087798498.8ed310@air.net.au>
Cc: Joel Brobecker <brobecker@gnat.com>,
Joe Buck <Joe.Buck@synopsys.com>,
Zack Weinberg <zack@codesourcery.com>,
gcc@gcc.gnu.org, gdb@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: PROPOSAL: removing src/expect
Date: Wed, 16 Jun 2004 07:08:00 -0000 [thread overview]
Message-ID: <or7ju80yl0.fsf@livre.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20040616161454.A26988@mailhub.air.net.au>
On Jun 16, 2004, Ben Elliston <bje+dated+1087798498.8ed310@air.net.au> wrote:
> I meant who is going to keep src/expect up to date? The version
> that's there has not been touched since the initial sourceware import
> in November 1999.
Do we have evidence that it's broken? If so, we do need an update.
If not, why can't we just leave it at the working state?
Removing it just for the sake of having it gone will gain us nothing,
and will inconvenience those that rely on it. So, again, what's the
point?
As for who's going to keep it up-to-date, whoever finds that there are
problems in what's in there.
--
Alexandre Oliva http://www.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:[~2004-06-16 7:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 4:15 Ben Elliston
2004-06-15 20:35 ` Alexandre Oliva
2004-06-15 21:32 ` Zack Weinberg
2004-06-15 22:24 ` Alexandre Oliva
2004-06-15 22:29 ` Zack Weinberg
2004-06-15 22:56 ` Daniel Jacobowitz
2004-06-15 23:07 ` Andrew Cagney
2004-06-15 23:40 ` Andreas Schwab
2004-06-15 22:50 ` Joe Buck
2004-06-16 3:34 ` Alexandre Oliva
2004-06-16 3:35 ` Ben Elliston
2004-06-16 6:11 ` Joel Brobecker
2004-06-16 6:15 ` Ben Elliston
2004-06-16 7:08 ` Alexandre Oliva [this message]
2004-06-16 13:46 ` Andrew Cagney
2004-06-16 16:30 ` Joe Buck
2004-06-16 19:53 ` Alexandre Oliva
2004-06-16 22:48 ` Ben Elliston
2004-06-16 16:27 ` Joe Buck
2004-06-15 22:43 ` Ben Elliston
2004-06-15 4:37 Michael Elizabeth Chastain
2004-06-16 15:31 Michael Elizabeth Chastain
2004-06-17 3:24 Michael Elizabeth Chastain
2004-06-17 17:30 ` Christopher Faylor
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=or7ju80yl0.fsf@livre.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=Joe.Buck@synopsys.com \
--cc=binutils@sources.redhat.com \
--cc=bje+dated+1087798498.8ed310@air.net.au \
--cc=brobecker@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=zack@codesourcery.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