|Subject:||Re: Read only file|
|Date:||Tue, 8 Oct 2002 09:03:23 -0700 (PDT)|
Thanks a lot for the help :-) . But I am not able to understand why read only directory is required in CVS. Why can't we have directories which has both read and write permission and in that directories files with read only permission and some writable files too? Coz in normal unix this works perfectly fine. Could anyone explain it ?
Thanks and Regards,
Rob Helmer wrote:
On Mon, Oct 07, 2002 at 12:31:17PM -0400, Larry Jones wrote:
> dd hh writes:
> > Is it possible to have a file that can be checkout but
> > which cannot be committed or updated? If yes pl let me know how to do
> > it. It is required that once this file is checked out changes on the
> > particular file can be done on local directory but this file cannot be
> > commited back to the repository.Also on doing cvs update the changes
> > made in this file in local directory should not be lost .
> Yes and no. You can have read-only *directories* in the repository by
> setting the permissions to allow reading but not writing, but you can't
> have both read-only and writable files in a single directory. Update
> never loses local changes unless the user specifically requests it -- by
> default, it merges repository changes with the local changes and reports
> any resulting conflicts.
Yes, you are right, the file needs to be in a seperate directory, since
directory perms override file perms ( 'doh! ).
Info-cvs mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|