From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sourceware.cygnus.com
Subject: Re: replace (plain text)
Date: Wed, 04 Jul 2001 14:38:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010704142059.12750A-100000@cse.cygnus.com> (raw)
In-Reply-To: <01070422504300.01873@localhost.localdomain>
On Wed, 4 Jul 2001, Gacquer William wrote:
> Just a word about the cygnus CVS tree. Do you keep it secret cos your
> customers asked for custom developments that are visible in some cygnus tree
> branches? ( as Sony did for its Playstation 2 SDK, for instance, but that was
> a Cygnus Japan work )
>
> Having access to the whole tree would greatly simplify a lot of things for
> us.
The thing holding up CVS access is that fact that we have to get
both GDB and Source-Navigator upgraded to Tcl/Tk 8.3 before
they can exist in the same CVS repo on sources.redhat.com.
If you take a look at the current CVS module for Insight
you will note that it uses Tcl/Tk 8.0.
http://sources.redhat.com/insight/
Source-Navigator makes use of Tcl/Tk 8.1.
Once both Insight and Source-Navigator use the same version
of Tcl/Tk, we can add Source-Navigator to the CVS.
Mo
next prev parent reply other threads:[~2001-07-04 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 7:02 replace Aurelian Melinte
2001-07-03 13:12 ` replace Mo DeJong
2001-07-03 13:54 ` replace Gacquer William
2001-07-03 14:45 ` replace Mo DeJong
2001-07-03 15:32 ` SN +gvim + ex-ctags == excellent free IDE Subrata Datta
2001-07-03 18:37 ` replace (plain text) Berek Half-hand
2001-07-03 22:54 ` Eric Christopher
2001-07-04 11:49 ` Mo DeJong
2001-07-04 12:09 ` Berek Half-hand
2001-07-04 15:11 ` Eric Christopher
2001-07-09 7:17 ` Aurelian Melinte
2001-07-04 13:52 ` Gacquer William
2001-07-04 14:38 ` Mo DeJong [this message]
2001-07-04 15:10 ` Gacquer William
2001-07-05 18:21 ` Mo DeJong
2001-07-06 13:41 ` 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=Pine.SOL.3.91.1010704142059.12750A-100000@cse.cygnus.com \
--to=mdejong@cygnus.com \
--cc=sourcenav@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).