From: Steve Evans <stevee@gorbag.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Quanta setup for cervisia?
Date: Wed, 31 Aug 2005 00:16:33 +0100 [thread overview]
Message-ID: <200508310016.39539.stevee@gorbag.com> (raw)
In-Reply-To: <1125441590.12663.0.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
On Tuesday 30 August 2005 23:39, Jeff Cranmer wrote:
> I have been using Quanta to develop a small website. Apart from a
> tendency to die with 'sigsegv' crashes at regular intervals, the program
> seems to work quite well (the recovery function always manages to
> recover almost all my work after a crash).
>
> I would like to import the project into cervisia, so that I can maintain
> it via cvs and perform some kind of version control on the website, but
> I don't know how to set this up.
>
> Opening the project from Quanta and clicking on the cvs icon simply
> returns the error
>
> "This is not a CVS folder"
>
> I get a similar error when I try to open any folder from within
> konqueror. From konqueror, I can then go through a cycle of creating a
> project via cervisia, but next time I try to open that project from
> within konqueror, I get the same "This is not a CVS folder" error - back
> to square one :-/
>
> It seems that the first hurdle I need to get over is "How do you create
> a CVS folder?"
>
> Can anybody help me with this?
>
First you need to create a CVS repository containing the existing Quanta
project, using cvs import. Then checkout that repository somewhere with cvs
checkout. Finally use the newly checked out copy as the Quanta project.
However it sounds to me as though you first need to learn something about CVS.
There are many tutorials on the web, e.g.
<http://www.osnews.com/story.php?news_id=6096> which is targetted at people
using Cervisia, or
<http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/cvs/> which is a more
general purpose tutorial.
Steve
--
____________________________________________________________________
Steve Evans E-mail: mailto:stevee@gorbag.com
WEB: http://www.gorbag.com
Registered Linux user #217906: http://counter.li.org
Public Encryption Key: http://www.gorbag.com/public-key.html
____________________________________________________________________
2.6.12-gentoo-r9 Intel(R) Pentium(R) 4 CPU 3.00GHz GNU/Linux
00:05:13 up 13 days, 15:52, 8 users, load average: 0.15, 0.14, 0.09
Saint: A dead sinner revised and edited.
-- Ambrose Bierce
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-30 23:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1116165126.23106.16.camel@tux>
2005-07-30 12:43 ` [gentoo-user] Shorewall failure following upgrade Jeff Cranmer
2005-07-30 13:17 ` Rumen Yotov
2005-07-30 23:09 ` Jeff Cranmer
2005-08-01 13:23 ` Dave Nebinger
2005-08-28 17:45 ` [gentoo-user] Quanta setup for cervisia? Jeff Cranmer
2005-08-30 22:39 ` [gentoo-user] " Jeff Cranmer
2005-08-30 23:16 ` Steve Evans [this message]
2005-10-29 20:26 ` [gentoo-user] Trying to install a cable modem connection Jeff Cranmer
2005-10-29 19:05 ` Michael Kjorling
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=200508310016.39539.stevee@gorbag.com \
--to=stevee@gorbag.com \
--cc=gentoo-user@lists.gentoo.org \
/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