<>
> >
> > I moved the source to a different machine where I
> had
> > set up a new repository. I edited the headers of
> the
> > files that had been checked in before, deleting
> the
> > expanded $ID$ information. I then proceeded to do
> a
> > standard ``cvs import`` of my project. I then
> chec
Charles Baker wrote:
>
> Are there any cvs guru's on the list? I had some files
> that had previously been checked into cvs. There were
> also some files in the same project which had not been
> checked in ever.
>
> I moved the source to a different machine where I had
> set up a new repository.
Are there any cvs guru's on the list? I had some files
that had previously been checked into cvs. There were
also some files in the same project which had not been
checked in ever.
I moved the source to a different machine where I had
set up a new repository. I edited the headers of the
files that
On Wed, Jun 13, 2001 at 10:16:43PM -0400, Noah L. Meyerhans wrote:
> I thought I found the answer to this question a while back, but I either
> misplaced it or was mistaken.
>
> Basically what I need to do is create symlinks on a source check out.
> The repository contains a file foo, and I need a
On Wed, Jun 13, 2001 at 09:44:23PM -0400, Brenda J. Butler wrote:
>
> In the CVSROOT/modules file, define your module like so:
>
> myproj-o "ln -s bar foo" myproj
Yes, I think that is what I was looking for. Though you're right that
-o needs to be given a single argument. Accoring to t
On Wed, Jun 13, 2001 at 10:16:43PM -0400, Noah L. Meyerhans wrote:
> I thought I found the answer to this question a while back, but I either
> misplaced it or was mistaken.
>
> Basically what I need to do is create symlinks on a source check out.
> The repository contains a file foo, and I need a
I thought I found the answer to this question a while back, but I either
misplaced it or was mistaken.
Basically what I need to do is create symlinks on a source check out.
The repository contains a file foo, and I need a symlink bar -> foo. Is
there any way to ensure that this link is created ev
On Mon, Apr 10, 2000 at 05:17:39PM -0400, Brian Lavender wrote:
> Here is how I backed up. I was on version 1.7, so I deleted the file I had. I
> then
> did a cvs checkout -r 1.6 which warned me that the current file had been
> deleted,
> but gave me 1.6.
>
> I made my changes, but now and can't
Brian Lavender <[EMAIL PROTECTED]> writes:
> I have been using cvs to track development of the my latest tk/perl
> application. I have been coding along starting with version 1.1
> cruising along and making commits along the way. I got up to version
> 1.7 when I realized that I wanted to back up to
I have been using cvs to track development of the my latest tk/perl
application. I have been coding along starting with version 1.1 cruising
along and making commits along the way. I got up to version 1.7 when I realized
that I wanted to back up to version 1.6 make some changes, and continue from
David Morris wrote:
>
> I decided to give cvs a try on a programming project I am about ready to
> get started on and thought it easier to start from the beginning with the
> cvs setup. So I installed the cvs package this morning. However, I have
> what must be a very basic FAQ, but I can't find t
Hi,
File: cvs.info, Node: Creating a repository, Next: Backing up, Prev: Multipl\
e repositories, Up: Repository
Creating a repository
=
To set up a CVS repository, first choose the machine and disk on
which you want to store the revision history of the source files.
I decided to give cvs a try on a programming project I am about ready to
get started on and thought it easier to start from the beginning with the
cvs setup. So I installed the cvs package this morning. However, I have
what must be a very basic FAQ, but I can't find the answer to it in the
FAQ.
I
13 matches
Mail list logo