Re: read-only checkout when developer has no commit access

On Mon, Jul 24, 2000 at 09:02:24PM -0700, Niels P. Mayer wrote:
>...
> > Note also that I could perform local mods, be added to the access list, and
> > *then* check in. No determination about the authority to check in is
> > possible prior to the moment I check in.
>
> If you can do all that, then certainly a chmod u+w can be done too!
>
> I mean, how hard is it to go "find . -type f -exec chmod u+w {} \;" if
> you're lazy, or just chmod the individual files you modify.

The problem is that this needs to be done after every update. It
continuously reverts them back to read-only.

The behavior is a total pain in the ass. Forget the whole thing about "I
could edit, get access, then commit." Think about it people... how do you
generate a patch for somebody who already has commit access? :-)

In my case, I was trying to fix a bug in an SVN Makefile. Bam! Read-only.
*curse* Switch emacs, edit the sucker, do the chmod from a shell, then write
the file. Generate the diff. Email the diff.

Then I ran into it again, moments later while trying to do another diff.

And then I did a "cvs update" and went for more mods to the Makefile. Read
only again. #&*#^%$*

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/