> What Paul means is that he's added a new file to his tree, and wants to send > in a patch that includes that file. Unfortunately, CVS can't do that :P You > have two choices: > > - 'cvs add' the file, but don't commit. This is kinda lame since it requires > commit access, and it creates the administrativia for the file already. I > *think* that if you do this, only you can actually add the file (after the > patch is accepted ;) but I'm not sure. After the cvs add, a cvs diff -c will > show the file (as all +'es, obviously) even though it will complain to > stderr about its ignorance about that specific file. No, cvs diff still won't diff the file -- it says "new file". > - Don't use cvs diff. Use real diff instead. Something like this: Too much work to create a new tree. What I do: I usually *know* what are the new files. (If you don't, consider getting a little more organized first :-). Then do a regular diff -c between /dev/null and each of the new files, and append that to the CVS-generated diff. Patch understands diffs between /dev/null and a regular file and understands that this means to add the file. (I have no idea what the rest of this thread is about. Dinkytoy attitude??? I played with tpy cars called dinky toys, but I don't see the connection. What SF FAQ are we talking about anyway?) --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4