Re: Certain files are checkouted as read-only. Don't know why?

[Todd Denniston]

krevathi1912 wrote, On 12/31/2007 01:24 AM:
> But it doesn't help me. Still the files are checkout as read-only mode

I did not mean that the commands below would fix the issue, only that they 
might help you and us be sure of what the issue is.

if it is watchers, then you need to first have anyone who _IS_ currently 
"watching" a file to run `cvs watch remove` then you can start again, IIRC.

> Todd Denniston wrote:
> > krevathi1912 wrote, On 12/19/2007 08:26 AM:
> > > Hi,
> > >
> > > We have a CVS where a large no of codes are checked in all the days.
> > > Today files in the ceratain directory alone is checkout as readonly for
> > > all
> > > the users.
> > > I am sure no specific restriction is applied on these files.
> > > We dont know what is the reason for it. WE are unable to rectify it also.
> > > Any one help us to rectify this problem. 
> > > How to remove the read-only restriction on these files.
> > >
> > >
> > >
> > > Regards
> > > Revathi
> > in the directory where these files are read only, try the following
> > command:
> > cvs watchers -R
> >
> > I expect you will find someone has used the `cvs watch` command, I did not 
> > think it was supposed to make things RO but it has for me in the past. My 
> > solution for folks who wanted to watch files was to make a script that
> > always 
> > applied watches as `cvs watch add -a commit filename`, and have them use
> > that.
> >
> > or someone may have used `cvs edit` unnecessarily.

--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter