|
From: | Todd Denniston |
Subject: | Re: add a file without write perms on the repository |
Date: | Thu, 05 Oct 2006 08:41:56 -0500 |
User-agent: | Thunderbird 1.5.0.7 (X11/20060909) |
Jeremie Le Hen wrote:
Hi there, I am often working with CVS of various open-source projects on which I only have a read-only repository access. Sometimes, I want to write a patch that needs to create a new file in the project source tree. I am naturally expecting to be able to generate the patch with the following command: % cvs diff -upN Unfortunately, for -N to work the file has to be added to the project with the "cvs add" command which requires write permissions. I found a workaround for this. I simply modify CVS/Entries manually and add the following line (for protector.c, for instance): % /protector.c/0/Initial protector.c// Is there any way to achieve this, without hacking CVS/Entries manually ? If not, is it acceptable to add a new option to the "add" command to achieve this target ?
Why yes there is. :}first you add yet another open-source project that you only have read-only repository access to your list. :0 Then you try to get any patches others may have stared relating to the following threads:
http://lists.gnu.org/archive/html/info-cvs/2005-01/msg00257.html http://lists.gnu.org/archive/html/info-cvs/2005-01/msg00244.html http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=add+hook+question+%28was&submit=Search%21&idxname=info-cvs&max=20&result=normal&sort=date%3AearlyThen you try to put the partial patches (if any exist) together with the ideas in the threads above, and make a huge patch (with documentation updates) that will get you lauded for all time when you get it committed.
I hope you enjoyed the humor I tried to put in this message. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter
[Prev in Thread] | Current Thread | [Next in Thread] |