Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gp@suse.de>
To: Ben Elliston <bje@wasabisystems.com>
Cc: Andrew Cagney <cagney@gnu.org>,
	gcc@gcc.gnu.org, gdb@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: DejaGnu 1.4.4 release
Date: Thu, 05 Feb 2004 20:50:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0402052145120.23473@lifschitz.suse.de> (raw)
In-Reply-To: <87llnhb6sq.fsf@wasabisystems.com>

On Thu, 6 Feb 2004, Ben Elliston wrote:
>> - should src/dejagnu/ be replaced?
> IMHO, yes.  The 1.4.4 release is very close to the version in
> src/dejagnu.  I've since merged a handful of patches from src -> FSF
> that were missed and I've a patch that can be applied after a 1.4.4
> import that will ensure that nothing will be lost from src/dejagnu.

Thanks!

>> - should src/dejagnu/ be removed?
> What would the alternative be?  To just expect (ha!) developers to
> have DejaGnu installed on their systems?

Yes.  If not right away, than in the mid term: we require casual
testers of CVS GCC to have bison and developers to have autoconf
etc.; and if upstream DejaGnu "just works", let's use that.

Most distributions will provide DejaGnu as a package anyway.

Gerald
-- 
Gerald Pfeifer <gp@suse.de>    Technical Project Manager, SUSE Linux AG


  reply	other threads:[~2004-02-05 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2004-02-05 23:01       ` Joe Buck
2004-02-01  2:02 Michael Elizabeth Chastain
2004-02-05 23:21 Michael Elizabeth Chastain

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=Pine.LNX.4.58.0402052145120.23473@lifschitz.suse.de \
    --to=gp@suse.de \
    --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