public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Eray Ozkural <erayo@cs.bilkent.edu.tr>
To: Mo DeJong <supermo@bayarea.net>,
	sourcenav <sourcenav@sources.redhat.com>
Subject: Re: New CVS module to checkout.
Date: Thu, 21 Feb 2002 18:17:00 -0000	[thread overview]
Message-ID: <E16e56T-0000g2-00@orion.exa.homeip.net> (raw)
In-Reply-To: <20020221153419.6a2d3d26.supermo@bayarea.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Mo!

On Friday 22 February 2002 01:34, Mo DeJong wrote:
>
> 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.
>

So you might already like "sourcebase" name which I'd offered earlier? For 
specific databases usually this sort of compound word is used. For instance 
"knowledge base", "media base", etc...

If you agree, let's use "sourcebase".

Thanks,

- -- 
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo
GPG public key fingerprint: 360C 852F 88B0 A745 F31B  EA0F 7C07 AE16 874D 539C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8daekfAeuFodNU5wRAmnyAKCC5tzOeX1Gcf8kcfgMVgF8OyOspQCgkOQ6
JV5NsXx3Q2xucPm4HzcHDGg=
=dSsV
-----END PGP SIGNATURE-----

  reply	other threads:[~2002-02-22  2:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 16:12 Ian Roxborough
2002-02-20 17:51 ` Mo DeJong
2002-02-21  1:51   ` Mo DeJong
2002-02-21 14:48 ` Eray Ozkural
2002-02-21 15:35   ` Ian Roxborough
2002-02-22  0:16     ` Eray Ozkural
2002-02-22  2:43       ` Mo DeJong
2002-02-21 16:43   ` Mo DeJong
2002-02-21 18:17     ` Eray Ozkural [this message]
2002-02-22  8:16 Doug Fraser
2002-02-22 10:05 ` Eray Ozkural
2002-02-22 11:08 ` Gilles J. Seguin
2002-02-22 13:07   ` Ian Roxborough
2002-02-22 10:26 Doug Fraser
2002-02-22 13:55 ` Khamis Abuelkomboz

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=E16e56T-0000g2-00@orion.exa.homeip.net \
    --to=erayo@cs.bilkent.edu.tr \
    --cc=sourcenav@sources.redhat.com \
    --cc=supermo@bayarea.net \
    /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).