From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: DejaGNU
Date: Sat, 30 Dec 2006 18:29:00 -0000 [thread overview]
Message-ID: <upsa11bm9.fsf@gnu.org> (raw)
In-Reply-To: <20061230175914.GA20683@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 30 Dec 2006 12:59:14 -0500)
> Date: Sat, 30 Dec 2006 12:59:14 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb@sources.redhat.com
>
> On Sat, Dec 30, 2006 at 07:56:30PM +0200, Eli Zaretskii wrote:
> > gdb/README says that DejaGNU can be found on
> > ftp://sources.redhat.com/pub/dejagnu/, but there's no directory
> > pub/dejagnu on the sourceware FTP site. What is the right place to
> > look for it, and should README be fixed to point to that place?
>
> I would recommend ftp://ftp.gnu.org/gnu/dejagnu/, and probably the
> README should be updated.
gdb/README says that source.redhat.com will contain a recent snapshot
of DejaGNU, not its official release. ftp.gnu.org holds official
releases; the last DejaGNU there is from 2002. That's why I wanted to
see if a newer version was available from sourceware.
Are you saying that snapshots are no longer available from sourceware?
Is there any other place to look?
next prev parent reply other threads:[~2006-12-30 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 17:56 DejaGNU Eli Zaretskii
2006-12-30 17:59 ` DejaGNU Daniel Jacobowitz
2006-12-30 18:29 ` Eli Zaretskii [this message]
2006-12-31 2:23 ` DejaGNU Daniel Jacobowitz
2006-12-31 10:11 ` DejaGNU Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2002-11-20 12:22 dejagnu bemis
2002-11-20 20:37 ` dejagnu Andrew Cagney
2002-12-05 16:26 ` dejagnu Fernando Nasser
2002-12-05 16:58 ` dejagnu bemis
2002-12-05 17:08 ` dejagnu Fernando Nasser
2002-12-12 22:26 ` dejagnu 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=upsa11bm9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.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