Re: Setting the rules and politics for CVS...
Jim.Hyslop [EMAIL PROTECTED] schrieb im Newsbeitrag news:[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I´m studying CVS for the first time. I know how to use it now, but I don´t know how to make or config the rules and politics to make a group of about 5 programmers working in the repository. I will be the project leader... Do you know a doc or some URL, tutorial or URL with that info? The CVS Book (Open Source Development with CVS, 3rd Edition, by Karl Fogel and Moshe Bar) might be helpful. The book is GPLed and available in print and online at http://cvsbook.red-bean.com/cvsbook.html It covers real life problems and e.g. a chapter titled Going Out On A Limb (How To Work With Branches And Survive) HTH Martin ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Is there a way to Auto-Watch ?
Is there a way to enable file watching automatically or am I going to have to cobble up some sort of a crufty cron script ? Thanks. ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is there a way to Auto-Watch ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan White [EMAIL PROTECTED] writes: Is there a way to enable file watching automatically or am I going to have to cobble up some sort of a crufty cron script ? That depends on what kind of watching you want. https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_10.html#SEC89 -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFBCSCn3x41pRYZE/gRArOfAJ4vN0Me/C0XEuBH7L0cCVCFil52uQCdHTr2 0a1wEUvWMmSxlPBCcJ5O5Gw= =TU/X -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Help Setting up WinCVS with SSH
Hello everyone, I have a WinCVS running here on my computer and a server running Unix I have configured SSH as per many tutorials, set the environment variables correctly, set CVS variables right, created keys and authorized them on the server, and then I try to checkout a module in WinCVS, but I receive this: cvs [checkout aborted]: end of file from server (consult above messages if any) I tried to setup ssh for no passwords needed but what happens is a box pops up (black box) in the background whenever WinCVS connects to the host. At least the host is working right. If I try to connect to the server through ssh in command prompt I get the following problems: SSH Version 1.2.14 [winnt-4.0-x86], protocol version 1.4.Standard version. Does not use RSAREF.ssh_connect: getuid 0 geteuid 0 anon 0Connecting to Connection established.Remote protocol version 1.99, remote software version OpenSSH_3.4p1Waiting for server public key.Received server public key (768 bits) and host key (1024 bits).Hostis known and matches the host key.Initializing random; seed file C:\ssh-1_2_14-win32bin\home/.ssh/random_seedIDEA not supported, using 3des instead.Encryption type: 3desSent encrypted session key.Received encrypted confirmation.Doing password authentication. I am fairly certain I am NOT suppoed to have to do password authentication. Could anyody give me some idea how to fix this and get these files Checked out! Thanks, James [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is there a way to Auto-Watch ?
The task manager has decreed that all changes to all files will be checked in on a daily basis. (Despite the attempted reasoning about how CVS ain't built that way) So, we need to have all files watched, and set to notify the Build Manager role account when folks edit, unedit, and commit. I envisioned a cron script, run from the build manager account that does a mass checkout/watch on/watch add. But that strikes me as criminally kludgy. Is there a better way to do it ? Thanks. On Thu, 29 Jul 2004, Mark D. Baushke wrote: Dan White [EMAIL PROTECTED] writes: Is there a way to enable file watching automatically or am I going to have to cobble up some sort of a crufty cron script ? That depends on what kind of watching you want. https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_10.html#SEC89 -- Mark ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is there a way to Auto-Watch ?
At 01:05 PM 7/29/2004, Dan White wrote: The task manager has decreed that all changes to all files will be checked in on a daily basis. (Despite the attempted reasoning about how CVS ain't built that way) Give everyone a branch to work on and let them commit whenever they want. When they are ready to add to the baseline, have the task manager :-) perform the merge to the HEAD. Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is there a way to Auto-Watch ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan White [EMAIL PROTECTED] writes: The task manager has decreed that all changes to all files will be checked in on a daily basis. (Despite the attempted reasoning about how CVS ain't built that way) So, we need to have all files watched, and set to notify the Build Manager role account when folks edit, unedit, and commit. Your Build Manager sounds more like a micromanager. I hope there is a good reason for the process you have been told to follow. I envisioned a cron script, run from the build manager account that does a mass checkout/watch on/watch add. But that strikes me as criminally kludgy. Is there a better way to do it ? You probably only need to add new 'watch' statements as new files are added to the system. So, something that is wired into the 'loginfo' to look for new files and have them watched might be the way to go. I don't understand why a cron script would be needed... -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFBCTKP3x41pRYZE/gRAtYmAJ0Sa8OV/3i7p7MrqrptxszZXB+GhACfYuSy MHOvWyiOPO0unYjkZd3ddUQ= =fkMe -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is there a way to Auto-Watch ?
Mark D. Baushke writes: You probably only need to add new 'watch' statements as new files are added to the system. So, something that is wired into the 'loginfo' to look for new files and have them watched might be the way to go. Is that necessary? Doesn't watching a directory automatically watch any new files in that directory? -Larry Jones No one can prove I did that!! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is there a way to Auto-Watch ?
On Thu, 29 Jul 2004, Mark D. Baushke wrote: Dan White [EMAIL PROTECTED] writes: The task manager has decreed that all changes to all files will be checked in on a daily basis. (Despite the attempted reasoning about how CVS ain't built that way) So, we need to have all files watched, and set to notify the Build Manager role account when folks edit, unedit, and commit. Your Build Manager sounds more like a micromanager. I hope there is a good reason for the process you have been told to follow. Your perception is right on the mark. The good reason is 'cause he is the boss. I envisioned a cron script, run from the build manager account that does a mass checkout/watch on/watch add. But that strikes me as criminally kludgy. Is there a better way to do it ? You probably only need to add new 'watch' statements as new files are added to the system. So, something that is wired into the 'loginfo' to look for new files and have them watched might be the way to go. I don't understand why a cron script would be needed... I'll explore that. Cron was considered as a brute-force approach. If brute force does not work, it is only because it is being applied in an insufficient quantity. Thanks. ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is there a way to Auto-Watch ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Larry Jones [EMAIL PROTECTED] writes: Mark D. Baushke writes: You probably only need to add new 'watch' statements as new files are added to the system. So, something that is wired into the 'loginfo' to look for new files and have them watched might be the way to go. Is that necessary? Doesn't watching a directory automatically watch any new files in that directory? I was under the impression that only file entries are put into the CVS/fileattr in the repository via a 'cvs watch add' command. I am also under the impression that adding a new directory with new files will not automagically inherit notify statements for the parent directory. -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFBCTpu3x41pRYZE/gRApQKAKC/ksrGoyED9YJVxTgn64jjxzLgfACgv62D k/YsYqbP9oYwrEz25hqeMO8= =xQuP -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is there a way to Auto-Watch ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan White [EMAIL PROTECTED] writes: On Thu, 29 Jul 2004, Mark D. Baushke wrote: Dan White [EMAIL PROTECTED] writes: The task manager has decreed that all changes to all files will be checked in on a daily basis. (Despite the attempted reasoning about how CVS ain't built that way) So, we need to have all files watched, and set to notify the Build Manager role account when folks edit, unedit, and commit. Your Build Manager sounds more like a micromanager. I hope there is a good reason for the process you have been told to follow. Your perception is right on the mark. The good reason is 'cause he is the boss. There will likely be other jobs available if the economy in your area. You may wish to consider that not all managers are control fanatics... I envisioned a cron script, run from the build manager account that does a mass checkout/watch on/watch add. But that strikes me as criminally kludgy. Is there a better way to do it ? You probably only need to add new 'watch' statements as new files are added to the system. So, something that is wired into the 'loginfo' to look for new files and have them watched might be the way to go. I don't understand why a cron script would be needed... I'll explore that. Cron was considered as a brute-force approach. Hmmm... the point is that I do not understand what you intended to do with your cron job. If brute force does not work, it is only because it is being applied in an insufficient quantity. Thanks. Good luck, -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFBCTs53x41pRYZE/gRAlrqAJ4uQdH/qD1OFf+RXpBHv6d5JdMPmgCfcjab 832d/3qbUgJqxf1rUwJxoBQ= =+UYR -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is there a way to Auto-Watch ?
On Thu, 29 Jul 2004, Mark D. Baushke wrote: Larry Jones [EMAIL PROTECTED] writes: Mark D. Baushke writes: You probably only need to add new 'watch' statements as new files are added to the system. So, something that is wired into the 'loginfo' to look for new files and have them watched might be the way to go. Is that necessary? Doesn't watching a directory automatically watch any new files in that directory? I was under the impression that only file entries are put into the CVS/fileattr in the repository via a 'cvs watch add' command. I am also under the impression that adding a new directory with new files will not automagically inherit notify statements for the parent directory. Your impression is accurate. I did a quick test (watch on dir) and the fileattr file contained a list of files in that directory. ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is there a way to Auto-Watch ?
On Thu, 29 Jul 2004, Mark D. Baushke wrote: Dan White [EMAIL PROTECTED] writes: On Thu, 29 Jul 2004, Mark D. Baushke wrote: Dan White [EMAIL PROTECTED] writes: The task manager has decreed that all changes to all files will be checked in on a daily basis. (Despite the attempted reasoning about how CVS ain't built that way) So, we need to have all files watched, and set to notify the Build Manager role account when folks edit, unedit, and commit. Your Build Manager sounds more like a micromanager. I hope there is a good reason for the process you have been told to follow. Your perception is right on the mark. The good reason is 'cause he is the boss. There will likely be other jobs available if the economy in your area. You may wish to consider that not all managers are control fanatics... Not an option at this time. I envisioned a cron script, run from the build manager account that does a mass checkout/watch on/watch add. But that strikes me as criminally kludgy. Is there a better way to do it ? You probably only need to add new 'watch' statements as new files are added to the system. So, something that is wired into the 'loginfo' to look for new files and have them watched might be the way to go. I don't understand why a cron script would be needed... I'll explore that. Cron was considered as a brute-force approach. Hmmm... the point is that I do not understand what you intended to do with your cron job. Something like this: cd scratchdir foreach project-in-the-repository cvs checkout project cvs watch on project cvs watch add project end If brute force does not work, it is only because it is being applied in an insufficient quantity. Thanks. Good luck, ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Is there a way to Auto-Watch ?
Mark D. Baushke wrote: Actually, it may be that 'cvs watch on' may be inherited, but 'cvs watch add' that is not. 'cvs watch add' is inherited. At least, it is in my current project - I added some new files yesterday, and 'cvs watchers' shows a list of people, including myself, and I know I haven't run 'cvs watch add' in that project for a *very* long time. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
moving repository to a new server
Greetings from Toronto: This is likely a newb question, as I am relatively new to cvs, but I have just built a new machine to be our new cvs server and want to copy over the repository. The old server (cvs 1.11.11) is running on red hat 7, and the new machine (cvs 1.11.17) is running Fedora core 2. Is copying the CVSROOT folder sufficient, or are the actual changes to files stored elsewhere? I'd really appreciate any help anyone could offer. Thanks in advance, -- Joe Goldman JCS Support Analyst MyCloe.com / On-Line Learning Solutions Tel: 416-964-3717 ext. 100 Tel: 1-800-683-8488 Fax: 416-964-2836 website: www.mycloe.com email: [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: moving repository to a new server
Joe Goldman writes: This is likely a newb question, as I am relatively new to cvs, but I have just built a new machine to be our new cvs server and want to copy over the repository. The old server (cvs 1.11.11) is running on red hat 7, and the new machine (cvs 1.11.17) is running Fedora core 2. Is copying the CVSROOT folder sufficient, or are the actual changes to files stored elsewhere? I'd really appreciate any help anyone could offer. You might try reading the manual -- the section on Moving a repository would seem to be particularly appropos: https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_2.html#SEC25 -Larry Jones From now on, I'm devoting myself to the cultivation of interpersonal relationships. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
