From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Make CVS default revision controller
Date: Thu, 22 May 2003 17:26:45 +0200 [thread overview]
Message-ID: <84smr780ju.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 87he7ndpyx.fsf@kruhft.vc.shawcable.net
Burton Samograd <kruhft@hotmail.com> writes:
> 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.
FWIW, I use CVS for my config files. Then it is very easy to use
them on different machines. I love it.
But I use the symlink trick. I wrote a Makefile that creates all the
necessary symlinks, and I use "make install" from time to time
whenever I think that the symlinks should be corrected.
--
This line is not blank.
next prev parent reply other threads:[~2003-05-22 15:26 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
2003-05-22 15:26 ` Kai Großjohann [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84smr780ju.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).