From: Harald Maier <maierh@myself.com>
Subject: Re: Make CVS default revision controller
Date: Thu, 22 May 2003 16:58:30 +0200 [thread overview]
Message-ID: <m3n0hfhvu1.fsf@ate.maierh> (raw)
In-Reply-To: se4r3ndx1h.fsf@crpppc215.epfl.ch
marcuirl <marcuirl@imap.no2this.cc> writes:
> kai.grossjohann@gmx.net (Kai Großjohann) writes:
>
>> Niels Freimann <nfreimann@firemail.de> writes:
>>
>>> the problem is that vc uses rcs if the directory is NOT under CVS
>>> control. If there is a chance to change this "behavior" to CVS
>>> please let me know.
>>
>> Why is this a problem? For CVS, you have to create a repository,
>> first. Then you have to create a working directory. Then you can
>> add files from inside that working directory.
>>
>> So you can't add a random file to CVS anyway.
>
> So then, let us rephrase the question:
>
> How do you go about setting up an `empty' repository?
Take a look at info: (cvs)From scratch
>
> 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?
Personally, I woud use for the dot files RCS.
Harald
next prev parent reply other threads:[~2003-05-22 14:58 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
2003-05-23 6:11 ` Kai Großjohann
2003-05-22 14:58 ` Harald Maier [this message]
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=m3n0hfhvu1.fsf@ate.maierh \
--to=maierh@myself.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).