Paul Sander <[EMAIL PROTECTED]> writes:
> On Jan 24, 2005, at 6:20 AM, [EMAIL PROTECTED] wrote:
> 
> > Todd Denniston <[EMAIL PROTECTED]> writes:
> > [...]
> >>> $ echo dummy > dummy.txt
> >>> $ cvs add -m" " dummy.txt
> >>> cvs [server aborted]: "add" requires write access to the repository
> >>
> >> Until the Fix that Greg described late last year is put in, you can (I
> >> think) trick cvs at least for files.
> >>
> >> ***begin cvs_trick_add
> >> #! /bin/bash
> >> echo " /$1/0/dummy timestamp//" >> CVS/Entries
> >> echo " cvs trick added $1 to the Entries file."
> >> ***end cvs_trick_add
> >>
> >> cvs_trick_add dummy.txt
> >
> > Thanks a lot for the trick, Todd! Though I usually try to avoid
> > temptation to edit CVS/ files manually, it seems that in this case it's
> > indeed easier than replicating of the whole project into another directory
> 
> > and using regular 'diff' to compare them.
> >
> > Glad to hear things are going to be changed in the (hopefully near)
> > future.
> 
> It's unclear if that particular change will be made, or if made
> whether or not it will stay. The requirement to supply add-time
> triggers has been identified (by a number of users), which requires a
> contact with the server. This has undergone some heated debate.

Well, the problem described is in fact not in contacting with server,
but in requiring write access to the repository.

Is there any sound reason why 'cvs add' and 'cvs remove' commands
require *write* access to the repo?

-- 
Sergei.



_______________________________________________
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs

Reply via email to