From: Benjamin Rutt <rutt+news@cis.ohio-state.edu>
Subject: Re: Make CVS default revision controller
Date: Thu, 22 May 2003 18:35:06 -0400 [thread overview]
Message-ID: <wc3fzn6r4o5.fsf@gamma.cis.ohio-state.edu> (raw)
In-Reply-To: 84smr780ju.fsf@lucy.is.informatik.uni-duisburg.de
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> 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.
When you say "symlink trick", do you mean that you have a directory
under CVS control, somewhere, anywhere, and the contents of that
directory are a bunch of symlinks which link to the real config file
location? This way, you have a single place to go (the above
mentioned directory) to 'cvs update' your config files when you have
committed them on a different machine, even though your actual config
files may be spread across various directories including $HOME,
$HOME/.ssh/, etc?
--
Benjamin
next prev parent reply other threads:[~2003-05-22 22:35 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
2003-05-22 17:21 ` Edward O'Connor
2003-05-22 22:35 ` Benjamin Rutt [this message]
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=wc3fzn6r4o5.fsf@gamma.cis.ohio-state.edu \
--to=rutt+news@cis.ohio-state.edu \
/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.