[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Common code base for different projects
|
From: |
Greg A. Woods |
|
Subject: |
Re: Common code base for different projects |
|
Date: |
Wed, 29 Aug 2001 18:32:38 -0400 (EDT) |
[ On Wednesday, August 29, 2001 at 17:33:55 (-0400), Arcin Bozkurt - Archie
wrote: ]
> Subject: Re: Common code base for different projects
>
> <html>
Please DO NOT EVER post HTML to public mailing lists.
(don't quote anything but what is absolutely necessary to maintain
context for your reply too!)
> Q) Without loosing the history for those files, how do I move them out
> of the current module, and create a seperate module for them. Would
> moving the ,v files in the repository do the job?
It all depends on the history of your repository, including how and when
it was created.
Why do you think you need to preserve "the history" of those files?
Why not start a new project with a canonical copy of those files?
(i.e. why not create a new module, check out an empty working directory
for them [cvs -f co newmodule], copy the files into the new working
directory and then add them all to the new repository with "cvs add"?)
--
Greg A. Woods
+1 416 218-0098 VE3TCP <address@hidden> <address@hidden>
Planix, Inc. <address@hidden>; Secrets of the Weird <address@hidden>
Re: Common code base for different projects, Paul Sander, 2001/08/29