all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Burton Samograd <kruhft@hotmail.com>
Subject: Re: Make CVS default revision controller
Date: Thu, 22 May 2003 14:29:52 GMT	[thread overview]
Message-ID: <87he7ndpyx.fsf@kruhft.vc.shawcable.net> (raw)
In-Reply-To: se4r3ndx1h.fsf@crpppc215.epfl.ch

marcuirl <marcuirl@imap.no2this.cc> writes:

> kai.grossjohann@gmx.net (Kai Großjohann) writes:
> How do you go about setting up an `empty' repository?

>From the cvs info file:
---------------------------------------------------------------------
   For a new project, the easiest thing to do is probably to create an
empty directory structure, like this:

     $ mkdir tc
     $ mkdir tc/man
     $ mkdir tc/testing

   After that, you use the `import' command to create the
   corresponding
(empty) directory structure inside the repository:

     $ cd tc
     $ cvs import -m "Created directory structure" yoyodyne/DIR yoyo
     start

   Then, use `add' to add files (and new directories) as they appear.

   Check that the permissions CVS sets on the directories inside
`$CVSROOT' are reasonable.
---------------------------------------------------------------------

> All I want is to put .emacs, .gnus etc under CVS now that I am more
> confident using it. And do this without importing the entire ${HOME}
> directory structure. A work around I have thought is to ln -s these files
> to others in a config/ But that will not fix the problem when in
> another directory I want to CVS just one file in that directory?

I would reccomend just using RCS if you want that.  CVS is a bit picky
sometimes and RCS offers most of the same features (CVS was built off
of RCS initially).  Instead of storing in CVSROOT it just puts the
version files in ./RCS directories, and provides full merging, version
diffing, branching, etc.  Don't throw away old tools just so you can
use trendy software when won't even need 10% of the features it
provides.

If you are convinced you need CVS I would reccomend reading the info
docs and googling for "The CVS Book". CVS is a bit of black magic and
you need to read up on how to use it before you can really get
anything out of it.

> Am I being really thick or something, educate me and help the others,
> please.

Nope, not thick.  Just need to do a bit of reading :)

-- 
burton samograd
kruhft@kruhft.dyndns.org
http://kruhftwerk.dyndns.org

  parent reply	other threads:[~2003-05-22 14:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20  8:35 Make CVS default revision controller marcuirl
2003-05-20  9:27 ` Stefan Monnier
2003-05-20 12:36   ` Niels Freimann
     [not found]   ` <mailman.6455.1053434411.21513.help-gnu-emacs@gnu.org>
2003-05-22  8:51     ` Kai Großjohann
2003-05-22 11:46       ` marcuirl
2003-05-22 13:53         ` Stefan Monnier
2003-05-22 15:24           ` Kai Großjohann
2003-05-22 14:29         ` Burton Samograd [this message]
2003-05-22 15:26           ` Kai Großjohann
2003-05-22 17:21             ` Edward O'Connor
2003-05-22 22:35             ` Benjamin Rutt
2003-05-23  6:11               ` Kai Großjohann
2003-05-22 14:58         ` Harald Maier
2003-05-22 15:22         ` Kai Großjohann
2003-05-23  8:26           ` marcuirl
2003-05-23 11:48             ` Benjamin Riefenstahl
2003-05-23 14:52             ` Stefan Monnier
2003-05-26  6:56               ` marcuirl

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=87he7ndpyx.fsf@kruhft.vc.shawcable.net \
    --to=kruhft@hotmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.