Dennis Jones writes:
>
> rm filename.ext # remove the binary file
> cvs rm filename.ext # remove the file from the repository
> cvs ci filename.ext # commit the remove
>
> remove the original file from the Attic
>
> cvs ad filename.ext # add the new text file
> cvs ci filename.ext # commit the add
>
> At this point, the repository is correct, and a 'cvs up -A' by the user gets
> him the correct file in his local trees. It's a little convoluted, but it
> seems to work.
If you're going to remove the repository file, there's no point in cvs
removing it first. Since the users are going to have to do update -A
anyway, I think I'd prefer just using cvs admin -kkv to remove the
binaryness from the existing repository file, update -A your working
directory, and then check in the new text file. That way, you don't
lose your existing revision history.
-Larry Jones
I don't see why some people even HAVE cars. -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
