Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Sorry, actually the inconsistant is just on the client side, the rcs on the server is quite good. What happened is: after using "cvs admin -o -r1.31" command to remove the revision, this revision is delete on the server, but the client is still on this revision (and will prevent you from making any submit). And I figured out a workaround for this: 1. save the changes made to the file 2. run cvs udpate -C to get a most recent copy 3. apply the changes back 4. run submit to check in all the changes (and it could succeed here since you get synced with the server) "Tom" <pxknet at gmail.com> news:f8gflo$pto$1 at paris.nodomain.org... > woo, I just tried it and find the rcs file was result in an inconsistant > condition. This command is really unsafe to use. scared...., how could > some command appear in the help manual unsafe to use. I recommend to > remove the command which is unsafe or show user a warning message both in > help docs and before execute the command the potential risk of using it. > > "Gerhard Fiedler" <lists at connectionbrazil.com> > news:1opqxnuxkxig4$.dlg at connectionbrazil.com... >> Arthur Barrett wrote: >> >>> There is a "cvs admin" command that will let an administrator destroy >>> your SCM integrity by removing a revision, however it has not been >>> tested in years and there are various reports that it can harm the >>> repository. >> >> Do we have an authoritative list of commands (command/option >> combinations, >> ...) that are considered tested and safe to use? If not, is anybody >> interested in creating one? If so, what would be a good procedure and >> format? >> >> Gerhard > >