From: Andrew Cagney <ac131313@cygnus.com>
To: brendan@dgs.monash.edu.au
Cc: gdb <gdb@sourceware.cygnus.com>,
"Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: Re: GDB and Insight CVS repositories.
Date: Wed, 18 Aug 1999 17:26:00 -0000 [thread overview]
Message-ID: <37BB4F1D.B589F664@cygnus.com> (raw)
In-Reply-To: <37BB482C.B50ADCBC@dgs.monash.edu.au>
Brendan Simon wrote:
>
> I've heard that tGDB and Insight have seperate CVS repositories. Is
> this true ?
Cygnus maintains an internal source base that contains both GDB and
Insight.
Sourceware has:
o a CVS repository with approved GDB sources
o Insight tar archives and patches
Since the Insight mods to GDB are not approved they are not allowed to
be put in the CVS repository that contains official GDB sources.
Setting up a further repository on sourceware that contains an
un-approved GDB and Insight is just getting (as you suggest) silly.
What happens when someone wants to add that Python interface (or even
perl...) are each of those going to end up in separate unofficial
repositories.
enjoy,
Andrew
next prev parent reply other threads:[~1999-08-18 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-18 16:56 Brendan Simon
1999-08-18 17:26 ` Andrew Cagney [this message]
1999-08-18 17:42 ` Stan Shebs
1999-08-18 18:30 ` Brendan Simon
1999-08-18 18:45 ` Andrew Cagney
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=37BB4F1D.B589F664@cygnus.com \
--to=ac131313@cygnus.com \
--cc=brendan@dgs.monash.edu.au \
--cc=gdb@sourceware.cygnus.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).