>Fernando Lopez writes:
>>
>> $ cvs admin -l config.cpp
>> RCS file: /boot/home/repositoriocvs/gnu/guavac/config.cpp,v
>> 1.3 locked
>> done
>>
>> When I got this file from another sandbox it's read-write
>
>I think the confusion is that admin -l makes the file read-only for
>other *users*, not the same user in a different sandbox.
>
>-Larry Jones
>
>I hate being good. -- Calvin
>
Thank you I found it.
I have another (the last problem). When I try to import RCS files into
CVS files as O'reilly CVS Pocket Refence book say at page 29 it don't
work. I copy ,v files directly over the repository ones. But if I update
it told me:
$ cvs update
cvs update: Updating .
cvs update: warning: FFTiterativo.c is not (any longer) pertinent
cvs update: warning: FFTiterativo.h is not (any longer) pertinent
cvs update: warning: FFTrecursivo.c is not (any longer) pertinent
cvs update: warning: FFTrecursivo.h is not (any longer) pertinent
cvs update: warning: Makefile is not (any longer) pertinent
cvs update: warning: complejo.c is not (any longer) pertinent
cvs update: warning: complejo.h is not (any longer) pertinent
cvs update: warning: estadisticas.c is not (any longer) pertinent
cvs update: warning: estadisticas.h is not (any longer) pertinent
cvs update: warning: invFFT.c is not (any longer) pertinent
cvs update: warning: invFFT.h is not (any longer) pertinent
The book says than ,v RCS files are compatible with CVS ,v files. Is't
truth?
-----------------------------------
This message was sent with the demo version of Postmaster, a BeOS mail client.
For more information, please visit http://kennyc.com/postmaster
_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs
