Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Discussion <gdb@sourceware.cygnus.com>
Subject: Dejagnu as part of repository?
Date: Thu, 28 Oct 1999 03:26:00 -0000	[thread overview]
Message-ID: <381824BF.BCE63370@cygnus.com> (raw)

Hello,

Should the GDB repository contain dejagnu?

A user wanting to run GDB tests could then just check out ``gdb
dejagnu'' and build instantly and run the tests.  I figure that while
dejagnu is a separate product the way GDB uses it is very like READLINE
in that it is imported and then locked in.

Thoughts?  Clearly there is the need to ensure that it is kept in sync
with GCC.

	Andrew
From law@cygnus.com Thu Oct 28 04:27:00 1999
From: Jeffrey A Law <law@cygnus.com>
To: ac131313@cygnus.com
Cc: gdb@sourceware.cygnus.com
Subject: Re: Dejagnu as part of repository? 
Date: Thu, 28 Oct 1999 04:27:00 -0000
Message-id: <24852.941109374@upchuck>
References: <199910281115.EAA10230@cygint.cygnus.com>
X-SW-Source: 1999-q4/msg00180.html
Content-length: 667

  In message <199910281115.EAA10230@cygint.cygnus.com>you write:
  > A user wanting to run GDB tests could then just check out ``gdb
  > dejagnu'' and build instantly and run the tests.  I figure that while
  > dejagnu is a separate product the way GDB uses it is very like READLINE
  > in that it is imported and then locked in.
  > 
  > Thoughts?  Clearly there is the need to ensure that it is kept in sync
  > with GCC.
You've got my vote.

Actually there is no sync problem since GCC doesn't have dejagnu in its
CVS repo.

Looking further out it is my opinion that we should be looking to move
more towards a single CVS repository for all these projects.

jeff


             reply	other threads:[~1999-10-28  3:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-28  3:26 Andrew Cagney [this message]
1999-10-28  7:53 ` J.T. Conklin
     [not found] <199910281115.EAA10230@cygint.cygnus.com>
1999-10-28  4:42 ` Pierre Muller

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=381824BF.BCE63370@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb@sourceware.cygnus.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