Am Mittwoch, 23. Juli 2003 15:48 schrieb Jon Lapham: > Today I (think I) committed my first CVS change (to gnucash-docs). > Thanks Derek, the problem was solve by re-checkingout the code.
Great. I'm a bit puzzled that there hasn't been a cvs notification email on gnucash-patches, but sometimes that seems to take some time. Or maybe [EMAIL PROTECTED] (which would be the sender of that message) is not yet subscribed to gnucash-patches, which will make your message hold back until the moderator adds you to the sender filter. > Does it look like I did it correctly? I'll check later. > Do people typically work inside the CVS checkout directory? Or, do you > make a copy of it and work in the copy? I directly work inside the CVS checkout directory. > When compiling, do you compile within the CVS checkout directory? (I > ask because cmpiling makes a bunch of new files, which I imagine we want > to keep out of CVS). As Nathan Neulinger already mentioned, the generated files won't affect CVS until you explicitly 'cvs add' them. And you can get rid of the warnings by adding the to-be-ignored files to the .cvsignore file in each directory. The only common problem here is that people easily forget to actually add new necessary files to CVS. The file exists locally, so their local compile will run without errors. But if they forget to add e.g. a new foo.c file to CVS, other people will run into the missing file errors after they updated their CVS copy. So usually it's not the problem that too many file make it into CVS accidentally, but rather too less :-) > How do you keep both the HEAD and v1.8 branches (I know how to check > them both out, but they use the same top level directory name)? Can you > rename (for example) the directory holding the v1.8 branch from > "gnucash" to "gnucash_1.8"? You can change the directory name of the top-level directory to everything you want -- you don't have to keep this to be "gnucash". So I have one source tree under the top-level directory "gnucash-HEAD" and another one in "gnucash-1-8" and another one in "gnucash-gnome". Simply checkout the appropriate branch and rename the top-level directory accordingly. Christian _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
