public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Syd Polk <spolk@redhat.com>
To: lstabile@concord.com, sourcenav@sources.redhat.com
Subject: Re: [presales+tim.w@redhat.com: Re: Source Navigator]
Date: Wed, 29 Nov 2000 18:45:00 -0000	[thread overview]
Message-ID: <4.2.0.58.20001129184557.01b1c2e0@pop.cygnus.com> (raw)
In-Reply-To: <200011291330.IAA27681@sandbox.concord.com>

This is an often-requested feature from sites with large amounts of source 
code. Right now, we don't support it very well.

It is on the (long) list of things to address.

At 08:30 AM 11/29/00 -0500, Larry Stabile wrote:
>Is there anything you can tell me about the questions below? Thanks.
>
>Larry Stabile
>Concord Communications, Inc.
>600 Nickerson Road
>Marlborough, MA 01752
>lstabile@concord.com
>508-303-4246
>
>------- Start of forwarded message -------
>Sender: tim@redhat.com
>Date: Mon, 20 Nov 2000 06:54:56 -0800
>Organization: Red Hat
>X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i686)
>X-Accept-Language: en
>MIME-Version: 1.0
>Subject: Re: Source Navigator
>References: <md5:96C89D43ACB5592CC36E25E1BD3A7D4B>
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>From: "tim.w" <presales+tim.w@redhat.com>
>To: presales+lstabile+concord.com@redhat.com
>X-Mailgate-Version: Mailgate v1.3
>Content-Length: 1520
>
>
> > I tried Source Navigator 4.5.2 and it looks pretty good.
> >
> > We have a source base of 1M+ lines of C++ code, so it takes awhile to
> > create a project database. I would like to be able to operate in the
> > following way:
> >
> >     1. Make an initial source pass.
> >
> >     2. Schedule a nightly job to update the project database.
> >
> >     3. Allow developers to see this "master" project database
> >        read-only from their desktop systems by accessing the shared
> >        project database and source code.
> >
> > We use Clearcase as our source control system.

Well, although there is something labelled "ClearCase" in Source-Navigator, 
it never worked for us, and we believe that it never worked for the 
original developers.

> >
> > The main question I have right now is whether the project database can
> > be updated incrementally -- i.e., by checking file modification times
> > or other methods. It would be expensive for us to scan the whole
> > source tree each night.

We already scan it incrementally. There are performance problems with 
deleting records from the underlying database that makes it horribly slow.

> >
> > Also, please comment on whether you think the above sharing
> > methodology is feasible. Note that I don't need a system right now
> > which can share a main database and incrementally update local
> > changes on developer's destktop machines. The main use of this will be
> > to give people a way to browse the general source structure, not as an
> > up-to-the-minute development tool.
>
>
>Larry,
>
>I have forwarded your concerns to the Source Navigator people. They can
>be contacted at...
>
>sourcenav@sources.redhat.com
>
>...if you have any other questions about Source Navigator.
>
>Thank you,
>
>- --
>Tim W.                  | "I don't care to belong to a club that
>Red Hat Presales        | accepts people like me as members."
>                         | --Grocho Marx
>------- End of forwarded message -------

Syd Polk		spolk@redhat.com
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.



  reply	other threads:[~2000-11-29 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-29  5:30 Larry Stabile
2000-11-29 18:45 ` Syd Polk [this message]
2000-11-29 19:59   ` Larry Stabile

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=4.2.0.58.20001129184557.01b1c2e0@pop.cygnus.com \
    --to=spolk@redhat.com \
    --cc=lstabile@concord.com \
    --cc=sourcenav@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).