revision control
Hello Everyone; This is my first time posting. I have been watching the interaction for a while, but I did not see that anyone recently had the problem I am having now. Problem: An individual has updated a bunch of files in a certain directory. This person was not supposed to update the files. All the files this person updated are all bad. Question: What is the best way to revert all the files back to the previous individual versions that were good? Thanks Bill Shields [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Check out trigger
Hello All, I am desperately trying to have a trigger set up for check out. What I have been able to do is to add the following line in the module file mod2 -o d:\myprog mod2 And what this does is it will fire the 'd:\myprog' script whenever any file from module 'mod2' is checked out. But what I am looking for is to have a trigger which will be called whenever any file is checked out from any module in the repository. All thoughts regarding this will be sincerely appreciated. I am running CVS 1.10.5 on NT Waiting for some ideas, Anand ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
source code for rcs57nt / cvs-1.9-win?
I am looking for the source code used to compile the exe's contained in rcs57nt.zip [which is a subset of the exe's in cvs-1.9-win.zip, and are also the same as the rcs exe's included with wincvs]. I am doing a daily conversion of a vss archive to cvs, using the vss2rcs.js script written by Curt Hagenlocher. [My group still uses VSS, but I want to have the speed [10x over the WAN] and flexibility of CVS, as well as seeing what it would take to convert.] Using the script, I notice that VSS does not mind it when a developer's computer's date is set to 2020, and the next version is in 2000, etc [I guess it is a 'feature' of not being client/server], but rcs's ci tool does care. So, I want to get the sources for the rcs exe's being used, to see if I can hack something together for short term usage. The problem is that I cannot find the source code used to compile these exe's. I have compiled rcs 5.7 [using the rcs57pc3.zip file from http://www.cs.purdue.edu/homes/trinkle/RCS/], but the exe's have different behavior than the ones in rcs57nt.zip [ie: ci wants repo files to be in an RCS subdir] Please don't tell me that rcs-5.7 is available in all sorts of places, as the source _is_ different, according to the Id tags in the exe's: strings ci_rcs57nt.exe |fgrep '$Id' $Id: rcsbase.h,v 5.20.1.2 1995/09/24 22:37:52 marka Exp $ $Id: ci.c,v 5.30.1.2 1995/08/08 00:48:30 marka Exp $ $Id: rcslex.c,v 5.19.1.1 1995/08/08 01:28:08 marka Exp $ $Id: rcssyn.c,v 5.15.1.1 1995/08/08 01:34:06 marka Exp $ ... vs strings ci_rcs57pc3.exe |fgrep '$Id' $Id: rcsbase.h,v 5.20 1995/06/16 06:19:24 eggert Exp $ $Id: ci.c,v 5.30 1995/06/16 06:19:24 eggert Exp $ $Id: rcslex.c,v 5.19 1995/06/16 06:19:24 eggert Exp $ $Id: rcsutil.c,v 5.20 1995/06/16 06:19:24 eggert Exp $ ... Does anyone know where I can get the full source, or a copy of the diffs which 'marka' had? [perhaps there is a cvs repository with this in it somewhere? I do not see it in the cvs repository.] thanks greg priem ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: source code for rcs57nt / cvs-1.9-win?
On Tue, 26 Sep 2000 14:16:14 -0700, Donald Sharp wrote: Why don't you just fix vss2rcs.js to check the date returned by vss and if it's greater than what could even remotely be possible change it to a sane value? Seems like a lot of work to hack cvs when you should just hack the input script... I probably should have mentioned that that was what i originally tried, but it got more complicated, since this is not just restricted to the year being goofy. [the 2020 stuff is not really difficult to take care of, as most of them were 'really' 1998. There are also some dates of 2000 (probably doing y2k testing and forgetting to turn the date back), which are not as easy to identify as being 'bad'] The complication can perhaps been seen in a multiple developer environment with the developers in multiple time zones, since VSS does not have any time-normalizing or control. Here is one sequence which is in our vss: 1. Developer A checks in source, 5pm his time, and then leaves for home. 2. Developer B [in time zone 1 hour behind developer A] finds bug in source, fixes it and checks it in, 4:30pm his time. catching and trying to fix all of them up would be a nightmare. much quicker, but less desirable, would be to use the current date/time when checking in the files, but then the full span of time would be lost in the conversion [oh - i fixed that bug while you were on sabbatical last year] with the rcs 5.7 ci.c source, it seems like it does a simple check for date, sends a message, and does a 'continue'. a simple commenting out of the continue may be a usable kludge. i figured, since rcs appears to be gpl, that source _should_ have been available at some point and someone might have it. greg priem kb0erz [EMAIL PROTECTED] bark, fido, bark [neither of us speak for my employer] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: source code for rcs57nt / cvs-1.9-win?
On Tue, Sep 26, 2000 at 02:50:24PM -0700, Gregory L Priem wrote: On Tue, 26 Sep 2000 14:16:14 -0700, Donald Sharp wrote: Why don't you just fix vss2rcs.js to check the date returned by vss and if it's greater than what could even remotely be possible change it to a sane value? Seems like a lot of work to hack cvs when you should just hack the input script... I probably should have mentioned that that was what i originally tried, but it got more complicated, since this is not just restricted to the year being goofy. [the 2020 stuff is not really difficult to take care of, as most of them were 'really' 1998. There are also some dates of 2000 (probably doing y2k testing and forgetting to turn the date back), which are not as easy to identify as being 'bad'] The complication can perhaps been seen in a multiple developer environment with the developers in multiple time zones, since VSS does not have any time-normalizing or control. Here is one sequence which is in our vss: 1. Developer A checks in source, 5pm his time, and then leaves for home. 2. Developer B [in time zone 1 hour behind developer A] finds bug in source, fixes it and checks it in, 4:30pm his time. catching and trying to fix all of them up would be a nightmare. much quicker, but less desirable, would be to use the current date/time when checking in the files, but then the full span of time would be lost in the conversion [oh - i fixed that bug while you were on sabbatical last year] with the rcs 5.7 ci.c source, it seems like it does a simple check for date, sends a message, and does a 'continue'. a simple commenting out of the continue may be a usable kludge. This will break other cvs commands. Lots of cvs commands depend on the date time stamp increasing from oldest-newest. With this kludge you'll be able to get the information in. But you will not be able to get the information out in a meaningfull manner. Suppose I have a file with these version- timestamps: 1.1 - 09-01-2000 1.2 - 08-01-2000 1.3 - 09-03-2000 1.4 - 09-04-2000 Now suppose I do a diff of this file versus the contents of the file on 09-01-2000. CVS now would only diff versus the 1.2 version of the file versus the correct version that would be 1.1. This is just one example of where cvs would fail. It's better to not be able to ask these questions instead of asking these questions and just getting *wrong* information. The more I think about it. If you can't guarantee the correct time as you import than you shouldn't import the time stamps( just say it's lost ). donald i figured, since rcs appears to be gpl, that source _should_ have been available at some point and someone might have it. greg priem kb0erz [EMAIL PROTECTED] bark, fido, bark [neither of us speak for my employer] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
