RE: how to extract two versions of file for comparison
Original Message From: Dave Korn Sent: 14 July 2005 14:31 Original Message From: NoPlatitudes Sent: 14 July 2005 14:16 I am trying to get the difference between the latest working version of a file and a previous version. I need to use a third party tool to examine this difference (cvs's diff functionality won't do what I want here). I want the newest version to remain in my 'standard' working directory, and I'd like the old version to be extracted (for reference only; no edits needed) to another directory, like /temp off of my working directory. How can I do this? cvs update -C -r rev -p file.name /temp/file.name Correction: Don't use -C or you'll end up with a spurious 'locally modified ... moved to ...' message as the first line of /temp/file.name. Apologies for the confusion! cheers, DaveK -- Can't think of a witty .sigline today ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: how to extract two versions of file for comparison
Original Message From: NoPlatitudes Sent: 14 July 2005 14:16 I am trying to get the difference between the latest working version of a file and a previous version. I need to use a third party tool to examine this difference (cvs's diff functionality won't do what I want here). I want the newest version to remain in my 'standard' working directory, and I'd like the old version to be extracted (for reference only; no edits needed) to another directory, like /temp off of my working directory. How can I do this? cvs update -C -r rev -p file.name /temp/file.name cheers, DaveK -- Can't think of a witty .sigline today ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: How can I administratively freeze a branch?
Original Message From: [EMAIL PROTECTED] Sent: 07 July 2005 11:09 Greetings. I have a project which was branched some time ago and now the branch has been merged back to HEAD. No further changes must be made to the old DEV2 branch, it is officially dead. Is there a way I can prevent developers from mistakenly committing to that branch (appart from deleting it)? Why not just cvs rm all the files from it, so they no longer exist at the head of the branch? People would have to accidentally checkout old revisions before they could accidentally commit to it; that's pretty improbable I think. cheers, DaveK -- Can't think of a witty .sigline today ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: error while installing CVS 1.11.20
Original Message From: ravish agarwal Sent: 06 July 2005 15:55 Please help me out. What is the possible cause of this error (Bundled) cc: warning 480: The -g option is available only with the C/ANSI C pro duct; ignored. (Bundled) cc: getpass.c, line 40: error 1705: Function prototypes are an ANSI feature. ^^^ Your compiler is twenty years out-of-date! Install gcc! cheers, DaveK -- Can't think of a witty .sigline today ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Don't commit during tagging
Original Message From: Stephan Lange Sent: 03 July 2005 19:25 Hey Folks! We are using cvs in an enterprise web-application development project. My task is the build and deployment of the new releases. The build will be making every week. Before I start the process I tag all the modules I need and then check out the modules with this tag. The tagging process needs time because some modules are very big. The question is, how can I be sure that during my tagging operation, no developer is committing some new stuff to the modules? http://catb.org/~esr/jargon/html/P/patch-pumpkin.html :) cheers, DaveK -- Can't think of a witty .sigline today ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
