[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs diff -uN - issue

From: J. Grant
Subject: Re: cvs diff -uN - issue
Date: Wed, 12 Mar 2003 01:53:00 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212


ok, not to worry about the mistake.

The above information is NOT correct.

These are the commands I have tested with:

$ cvs -d :pserver:address@hidden:/home/sdlweb/libsdl.org/cvs login
$ cvs -z3 -d :pserver:address@hidden:/home/sdlweb/libsdl.org/cvs
checkout SDL12
$ cd SDL12
$ cvs add README.PS2Linux
cvs [server aborted]: "add" requires write access to the repository
$ ll README.PS2Linux
-rwxr--r--    1 now3d    now3d         683 Mar  5 12:08 README.PS2Linux*

I can not see why "cvs add" does not work as a local operation in my
case.  Could you test this yourself and see if you also encounter this
problem please?

The 'cvs add' command appears to need to contact the server to determine
if the user is allowed to add files or directories to the repository. The
server indicates that the user is not allowed and spews the error message
you quoted above, this seems to be very itentional to make sure that you
don't do work that you are not able to commit.

hmm, this is rather a problem i think. I can not see a circumstance when this is really useful to disallow people to update their local copies of the repository...

Basically I develop patches for various projects, and I dont have cvs accounts. I want to "cvs diff" so that i send a patch updated against the latest src (without the issues of mainting a separate tree to diff against).

Could this be reconsidered to allow "cvs add" to modify the local copy of the repository please?

For myself, I typically develop patches based on a CVSup mirror of a
repository, but since I own all of the files, the 'add' and 'commit'
operations work fine. So, I never actually ran into your problem

> For the new directory, well, you could just do something like:
>     cvs diff -uNp > my-cvs.diffs
>     mkdir empty-directory
>     diff -uN empty-directory new-directory > my-new-directory.diffs
> and then massage the output of the two .diffs files into a single
> file for submission to whoever needs the patch.

Thanks, i managed to get a working patch using this method with -X

Yes, that is about the only workaround I can give you at present.

I regret the bad information I shared with you previously.

ok, thanks for following up on this.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]