public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@redhat.com>
To: bciceron@rsn.hp.com
Cc: sourcenav@sources.redhat.com
Subject: Re: cvs checkout
Date: Wed, 20 Jun 2001 11:54:00 -0000	[thread overview]
Message-ID: <3B30F091.C3E840BA@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106201333000.7548-100000@alaska.rsn.hp.com>

HEHe,
 ok I totally gave you the answer to a different question.... :-)
"Can I check sounce-navigator out of cvs? no... d'uh."

bciceron@rsn.hp.com wrote:
> let me ask you the same question for any project.
> snav allows us to use cvs as the source repo and look at cvs history or
> logs and also checkout but we cannot check out a project if it is not
> already part of it, can we ?

Correct.

> so the btom line is in order to to a cvs history on a file , of an
> existing project , i have to manually check out by doing cvs co on the
> command line then go to snav to do the retrieve the history.
> is there a shortcut allowing me to do thewhole thing from snav ?

Unfortunately not.  Maybe future version will let you create
SN project by browsing cvs reprositories and such, but for the
time being there are just somethings that our cvs feature doesn't
handle well.

Ian.

      reply	other threads:[~2001-06-20 11:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08 15:22 Can't build under 5.0 install/Linux Benjamin Scherrey
2001-06-15 14:10 ` Mo DeJong
2001-06-18 15:08   ` Benjamin Scherrey
2001-06-18 23:11     ` Mo DeJong
2001-06-19 14:56       ` Ralf Corsepius
2001-06-19 15:03         ` Mo DeJong
2001-06-20 14:14           ` Ralf Corsepius
2001-06-19 14:58       ` cvs checkout bciceron
2001-06-20 11:18         ` Ian Roxborough
2001-06-20 11:37           ` bciceron
2001-06-20 11:54             ` Ian Roxborough [this message]

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=3B30F091.C3E840BA@redhat.com \
    --to=irox@redhat.com \
    --cc=bciceron@rsn.hp.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).