public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@redhat.com>
To: Eray Ozkural <erayo@cs.bilkent.edu.tr>
Cc: sourcenav@sources.redhat.com
Subject: Re: New CVS module to checkout.
Date: Thu, 21 Feb 2002 15:35:00 -0000	[thread overview]
Message-ID: <3C758A9B.8D7B7C13@redhat.com> (raw)
In-Reply-To: <E16dzbH-0005s0-00@orion.exa.homeip.net>

Eray Ozkural wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Thursday 21 February 2002 02:04, Ian Roxborough wrote:
> > then just the normal:
> > cvs -d :pserver:anoncvs.cygnus.com:/cvs/sourcenav co snavigator
> > (gets Source-Navigator and the db.)
> >
> 
> 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.

Let me know when you've come up with a name and I'll create
a new module.  This one is just to make checking out tk/tcl/etc
a bit easier (since I hope more people will build it from CVS
soon).

On the matter of names, I'm stumped on a good name
for it.... libSN is about my limit.

Unless you want to call it something like phenix...
(IT, ginger?) ;-)

If I get a wave brain or something I'll post my ideas...

Ian.

  reply	other threads:[~2002-02-21 22:48 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 [this message]
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
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=3C758A9B.8D7B7C13@redhat.com \
    --to=irox@redhat.com \
    --cc=erayo@cs.bilkent.edu.tr \
    --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).