|Subject:||RE: CVS Import|
|Date:||Mon, 9 Jul 2001 13:17:41 -0400|
Thank you very much.
Works as expected.
From: address@hidden [mailto:address@hidden]
Sent: Monday, July 09, 2001 12:37 PM
Subject: Re: CVS Import
Rajesh Patwardhan writes:
> I use
> cvs import -m "Message" dir_to_import_on_cvs_repo vendor_tag release_tag_1
> The first import was good. There was no problem at all.
> 2) Now I do a import for the second source with
> cvs import -m "Message" dir_to_import_on_cvs vendor_tag release_tag_2
> This import also shows no errors.
It is a good idea at this point to do a merge checkout to detect any
files that were deleted between the two releases:
cvs co -jrelease_tag_1 -jrelease_tag_2 dir_to_import_on_cvs
cvs commit -m'merge'
> I do a cvs checkout in to another directory and in the status \ log do not
> see the versions as they should be seen or at least I think how they should
> i.e.: version with release_tag_1
> i.e.: version with release_tag_2
> I would expect a working revision of 18.104.22.168
If the file is exactly the same in both releases, CVS doesn't bother to
create a new revision, it just applies the new release tag to the
...That would be pretty cool, if they weren't out to kill me. -- Calvin
|[Prev in Thread]||Current Thread||[Next in Thread]|