[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Q: commit to new repo?
From: |
kj |
Subject: |
Re: Q: commit to new repo? |
Date: |
Fri, 14 May 2004 13:18:48 +0000 (UTC) |
User-agent: |
nn/6.6.5 |
In <address@hidden> "Frederic Brehm" <address@hidden> writes:
>At 03:58 PM 5/13/2004, kj wrote:
>>I have a whole bunch of source code that I have been committing to
>>one repository, and now I'm supposed to switch my commits to another
>>(pre-existing) repository (long story). I know that I can just
>>use "cvs -d <second_repo> import", but I'm concerned about losing
>>a lot of valuable revision history when I do this. Is there a way
>>to avoid this information loss?
>The history of the file "joe.java" that you have been working on is in a
>file in the original repository. Do a "cvs status joe.java" and look on the
>line "Repository revision:". It has the name of the repository file. It
>ends in the string "/joe.java,v".
>Simply copy the joe.java,v file from the original repository into the
>correct place in the new repository.
Wow! Let me make sure I have this straight: do you mean that
instead of doing
% cvs -d original_repo checkout myproj
% cd myproj
% cvs -d new_repo import myproj blah blah
...(and losing all history info in the process, I suppose) I could
simply do this
% cp -pr original_repo/myproj new_repo
??
What about removing a whole project with
% rm -rf cvs_repository/project_to_remove
? Would this mess up the rest of cvs_repository in any way?
Thanks!
kj
--
NOTE: In my address everything before the period is backwards.