From: Andrew Cagney <ac131313@cygnus.com>
To: sid@sources.redhat.com
Cc: GDB Discussion <gdb@sourceware.cygnus.com>
Subject: Dejagnu caretaker
Date: Mon, 15 Jan 2001 21:08:00 -0000 [thread overview]
Message-ID: <3A63D6C7.3D389BF5@cygnus.com> (raw)
Hello,
The top level MAINTAINERS file would suggest that the SID group have
laid claim to src/DEJAGNU, vis:
1.7 (fche 07-Dec-00): sid/, sid parts of cgen/, dejagnu/
1.7 (fche 07-Dec-00): sid:
http://sources.redhat.com/sid/
1.7 (fche 07-Dec-00): Patches to
sid@sources.redhat.com
interesting there is also:
1.1 (cagney 03-Apr-00): expect/, dejagnu/, config-ml.in,
mpw-README,
mpw-build.in,
1.4 (cagney 27-Jul-00): mpw-config.in, mpw-configure,
mpw-install, se
tup.com, missing,
1.4 (cagney 27-Jul-00): makefile.vms, utils/, config/,
config.if, mak
efile.vms, missing,
1.4 (cagney 27-Jul-00): ylwrap, mkdep, etc/, install-sh,
intl/
1.1 (cagney 03-Apr-00): ?
so I'm assuming that the intent was to indicate that SID have an active
interest in dejagnu.
The GDB group added that version of dejagnu to the binutils repository
when GDB was also incorporated. Since then they have been acting as the
unofficial caretakers of that code (since the official code is
elsewhere). If there is going to be something more formal established
then it would be appreciated if it was discussed first. GDB testing is
seriously dependant on dejagnu and really needs a finger in that pie.
GCC and binutils are probably not far behind in the queue.
I'll separate dejagnu from the SID categories.
enjoy,
Andrew
next reply other threads:[~2001-01-15 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 21:08 Andrew Cagney [this message]
2001-01-15 21:11 ` Ben Elliston
2001-01-16 1:09 ` Andrew Cagney
2001-01-16 8:47 ` Fernando Nasser
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=3A63D6C7.3D389BF5@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).