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

hi Ian and y'all,

thx for you answer,
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 ?
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 ?

thx,
ben-

On Wed, 20 Jun 2001, Ian Roxborough wrote:

-- bciceron@rsn.hp.com wrote:
-- >
-- > hello,
-- >
-- > i cannot find a way to check out a file from cvs if the object is not
-- > already added to the project , am i right ?
-- 
-- Kind of, we don't have a cvs repository yet.
--
-- > if so this means i have to check out an entire module from cvs then create
-- > a project for snav (a GREAT product BTW) then add it .
-- >
-- > i was expecting to check out from cvs with snav then add...
-- 
-- We are working on it, however they are some tasks which we
-- are currently working on, like upgrading Insight (and test
-- tools, etc.) to run with the same version of Tcl/Tk Source
-- Navigator uses, before we can add Source-Navigator to cvs.
-- 
-- Source-Navigator should be in cvs some time over the
-- next month or two.
-- 
-- Ian.
-- 


Regards,
		ben-

---PIM Team Lead---Unix Web Dvlpmnt---ITApp Group---HP Rsn Tx---T497-4773




  reply	other threads:[~2001-06-20 11:37 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 [this message]
2001-06-20 11:54             ` Ian Roxborough

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=Pine.LNX.4.33.0106201333000.7548-100000@alaska.rsn.hp.com \
    --to=bciceron@rsn.hp.com \
    --cc=irox@redhat.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).