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.
Oliver Giesen wrote: > I'm about to write a WinCvs macro for changing the -k mode of selected > files. I want this macro to work both with older and newer CVS/NT > client and server versions. AFAIHU the procedure for doing this has > changed somewhere in between 2.0.51 and 2.0.58 : <.snip.> > Is there maybe some other way that would work both with GNU CVS/older > CVSNT releases and the newer CVSNT? Right. I guess I will now go for the following sequence of commands: cvs admin -k[whatever] file(s) (does nothing on CVSNT 2.0.58+) cvs update -k[whatever] file(s) (effectively does nothing on pre-2.0.58) cvs commit -f -m"changed k-option" file(s) (optional on pre-2.0.58) BTW: For documentation reasons: Which was the exact version when commit after update -k became required? While I'm at it, here's an idea: Currently, after the Update -k you effectively have uncommitted changes in your sandbox. Yet, cvs status still reports the file as up-to-date (that's why the -f is required on commit after all) and if you don't commit right away for some reason it's quite easy to miss this. Could there maybe be some way to make this more transparent? E.g. changing the timestamp info in the Entries file to something like "Pending option change" when the cvs up -k is done? Furthermore, the commandline reference for cvs up -A reads "Reset any sticky tags/date/kopts.". Yet, this is obviously no longer true (not sure if it ever was). You cannot reset the k-option once you've done the cvs update -k . AFAICT the only way to undo that without knowing what the previous k-option was is releasing the folder and checking it out anew... or am I missing something? Cheers, -- Oliver ---- ------------------ JID: ogiesen at jabber.org ICQ: 18777742 (http://wwp.icq.com/18777742)