From: DJ Delorie <dj@redhat.com>
To: bje+dated+1087085689.0c7113@air.net.au
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: top-level removal of dejagnu, expect
Date: Thu, 10 Jun 2004 02:15:00 -0000 [thread overview]
Message-ID: <200406100214.i5A2Ew3P031152@greed.delorie.com> (raw)
In-Reply-To: <20040610101446.B3128@mailhub.air.net.au> (message from Ben Elliston on Thu, 10 Jun 2004 10:14:46 +1000)
> I have asked the major players and got overwhelming support.
I'd feel more comfortable if you asked all the players, not just the
major ones. Call me paranoid ;-)
> Removing the directories from the modules file is broken, as you
> know. It should be possible to check those files out if they were
> included in a past tag (which they were).
Did this come up in the source control BOF?
> I stated at the GCC Summit that, as a DejaGnu maintainer, I will be
> responsive to urgent bug fixes.
I don't doubt you will, but I was referring to porting, not fixing.
Red Hat has a lot of internal ports that we support through our
in-tree dejagnu that are still under NDA.
next prev parent reply other threads:[~2004-06-10 2:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 23:23 Ben Elliston
2004-06-09 23:26 ` Daniel Jacobowitz
2004-06-09 23:29 ` Ben Elliston
2004-06-10 14:08 ` Andrew Cagney
2004-06-10 20:10 ` Ben Elliston
2004-06-11 3:44 ` Andrew Cagney
2004-06-11 3:51 ` Ben Elliston
2004-06-11 4:15 ` Andrew Cagney
2004-06-11 4:18 ` Daniel Jacobowitz
2004-06-09 23:40 ` DJ Delorie
2004-06-10 0:15 ` Ben Elliston
2004-06-10 0:38 ` Christopher Faylor
2004-06-10 2:15 ` DJ Delorie [this message]
2004-06-10 2:19 ` Ben Elliston
2004-06-10 2:30 ` DJ Delorie
2004-06-10 2:34 ` Ben Elliston
2004-06-10 2:41 ` DJ Delorie
2004-06-10 2:50 ` Ben Elliston
2004-06-10 14:03 ` Andrew Cagney
2004-06-14 20:31 ` Alexandre Oliva
2004-06-10 2:22 ` Ian Lance Taylor
2004-06-10 2:27 ` Ben Elliston
2004-06-10 2:31 ` DJ Delorie
2004-06-14 20:25 ` 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=200406100214.i5A2Ew3P031152@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=bje+dated+1087085689.0c7113@air.net.au \
--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