From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7961 invoked by alias); 21 Feb 2002 23:35:21 -0000 Mailing-List: contact sourcenav-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sourcenav-owner@sources.redhat.com Received: (qmail 7850 invoked from network); 21 Feb 2002 23:35:20 -0000 Received: from unknown (HELO shell4.bayarea.net) (209.128.82.1) by sources.redhat.com with SMTP; 21 Feb 2002 23:35:20 -0000 Received: from modrick (209-128-79-218.BAYAREA.NET [209.128.79.218]) by shell4.bayarea.net (8.9.3/8.9.3) with SMTP id PAA09197 for ; Thu, 21 Feb 2002 15:35:19 -0800 (envelope-from supermo@bayarea.net) Date: Thu, 21 Feb 2002 16:43:00 -0000 From: Mo DeJong To: sourcenav Subject: Re: New CVS module to checkout. Message-Id: <20020221153419.6a2d3d26.supermo@bayarea.net> In-Reply-To: References: <3C7439A5.210890F8@redhat.com> Organization: House of Mirth X-Mailer: Sylpheed version 0.4.99cvs6 (GTK+ 1.2.7; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2002-q1/txt/msg00100.txt.bz2 On Thu, 21 Feb 2002 22:13:53 +0200 Eray Ozkural wrote: > Is this where we're supposed to work on sn backend? Or should we arrange a > separate CVS module for that? Last, we hadn't decided on a name. > > Thanks, No, that is just the CVSROOT for the source code that implements SN. It depends on modules that are shared with gdb and other projects, but the code that is only used by SN is separated out. On the subject of a project name, how about sourceDB? That might get across the concept of turning your source code into a database of symbols that can be queried. cheers Mo