cvs plug-in for cold fusion mx
Hi, I would like to apologize at the onset for a not so much a cvs related question for the list. But here goes Does any one know of a CVS plug-in for Cold Fusion MX? I have tried to Google but did not help... Any help or a pointer in the right direction would be greatly appreciated. Regards, Rajesh ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Stop branch creation
Hello All, I was wondering if any one has implemented a script to stop branch creation by users other then a chosen few. I did search on Google, but did not get any results. Any help or pointers on how to get some information from the Taginfo hook will be greatly appreciated. When I did a trace I got a reason=add on both cases of creation of a tag as well as branch Tag. Regards, Rajesh ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: can rtag on an existing branch?
Title: RE: can rtag on an existing branch? But if I am sure what I want to tag is on the repository and I use cvs rtag -DNow tag_name module Does it have any disadvantage? Regards, Rajesh -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 05, 2002 11:26 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: can rtag on an existing branch? Dan Walter writes: Do I have to learn how to use the tag command instead of the rtag command to do this? Absolutely. You should almost *never* use rtag without a -r argument because there's no way to know exactly what revisions you're tagging. The tag command tags exactly the revisions you have checked out in your working directory. -Larry Jones I hate it when they look at me that way. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Can I temporarily stop commits to a directory
Title: Can I temporarily stop commits to a directory Hello, I know this is a weird request but we are moving some directories around and so need to stop only commits to the current directory so we can copy \ make the new directory and then cvs remove the files at the old places so the files can later on be modified at new location. ( I would like to clarify that maintaining the version history of these few files is not important but moving is more necessary) . Is it possible to temporarily restrict the commit access to these directories only. with say lock files so that people can still checkout and update the said directories. I tried putting #cvs.lock and this stops the checkout and update also. Thank you very much for your time. If this has been addressed elsewhere kindly point me in the right direction, I tried to search on Google, but may have missed the relevant document. Regards, Rajesh PS: Please copy the reply to me since I had to unsubscribe recently due to spam mail on the list.
RE: meaning of P?
Title: RE: meaning of P? Does CVS server decide about whether to send a patch or complete Update depending on the access method used. Since I observed that when I used pserver method the same file update was designated with P but in local access mode it was a U. Regards, Rajesh -Original Message- From: Felix Moedritscher [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 3:10 AM To: [EMAIL PROTECTED] Subject: Re: meaning of P? Larry Jones [EMAIL PROTECTED] wrote: Have you tried adding it to .cvsignore? Well, I added another .cvsignore in the directory itself and now it works ;-) Content of this .cvsignore: * Thx for all the hints, -- Felix Moedritscher | Email: [EMAIL PROTECTED] Student of Telematics | http://c-125.vc-graz.ac.at/~felix Graz University of Technology | - ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Retrieve lost file back
Title: Retrieve lost file back Hello All, I am trying to retrieve a file which was removed with a cvs remove. Environment is Solaris 7 and cvs 1.11 working in local mode. I am able to do a cvs log filename and the path given by cvs shows the file in attic. Now I do a cvs update -j removedversion -j removedversion -1 filename cvs updates the file into working directory and also points out some conflicts which I resolve and then try to -- commit --. The file I expect will come out from Attic and into the normal directory does not happen and still goes to the attic. Is it anything that I am doing anything wrong. ( As per the manual this should do it correctly and reinstate the file on the main development line ) or Is it a bug already fixed in the latest version? Thank you very much in advance for your time. Regards, Rajesh
RE: Retrieve lost file back
Title: RE: Retrieve lost file back Thanks for the response. Yes I tried to do multiple updates. And the last time there was a conflict but only due to $Id$ so that is not too bad to fix, but is there a way or a workaround since I am in a tight spot as I want this file back in the directory as well as on the same note there are one more problem. Some of the files from Windows machines were checked in to CVS. Now due to case insensitive ness on windows the file got into CVS as serverPage.java where it should have been ServerPage.java now when I try 1) remove the file serverPage.java and add ServerPage.java cvs complains that the file exists. Similarly I have a file TYpe.java which should have been Type.java. ( cvs 1.11 on solaris 7) Please do help me with a way to get the files with proper names in the cvs working directory not in the attic since as per your mail multiple tries of update have probably made it impossible to bring back into the working directory. ( Would a physical move of the files with proper file name from attic into working directory in the repository help as a last resort). Thank you once again for the help. Regards, Rajesh -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 01, 2001 11:32 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Retrieve lost file back Rajesh Patwardhan writes: I am trying to retrieve a file which was removed with a cvs remove. [...] Now I do a cvs update -j removedversion -j removedversion -1 filename cvs updates the file into working directory and also points out some conflicts which I resolve and then try to -- commit --. The file I expect will come out from Attic and into the normal directory does not happen and still goes to the attic. How can there be conflicts in this situation? Did you already have a version of the file in your working directory? There is a bug in CVS where doing multiple updates on a resurrected file removes the flag that tells CVS it needs to move it out of the Attic when committed. -Larry Jones There's never enough time to do all the nothing you want. -- Calvin
CVS Import
Title: CVS Import Hello, I went thru the Documentation for creating Import as well as FAQ. This is the scenario 1) I have a sources src_1, src_2, src_3 These are basically versions 1 2 3 of same code. Some files may have changed between the 3 versions. I am trying to import them into CVS as all the development is complete and CVS was not used during the Development of this Project. I use cvs import -m Message dir_to_import_on_cvs_repo vendor_tag release_tag_1 The first import was good. There was no problem at all. 2) Now I do a import for the second source with cvs import -m Message dir_to_import_on_cvs vendor_tag release_tag_2 This import also shows no errors. I do a cvs checkout in to another directory and in the status \ log do not see the versions as they should be seen or at least I think how they should be. i.e.: version with release_tag_1 i.e.: version with release_tag_2 I would expect a working revision of 1.1.1.2 I do not then try the 3rd Import. Conf: It is Red Hat Linux 7.0 cvs 1.11.1p1 (CVS Server) client 1.11 on Solaris 5.7 Result of cvs status -v dr.java File: dr.java Status: Up-to-date Working revision: 1.1.1.1 Repository revision: 1.1.1.1 path_in_repo/dr.java,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) Existing Tags: start_553 (revision: 1.1.1.1) gui (branch: 1.1.1) 2) or is there any better way of doing it. or some point I am missing. If I have missed out any data please do let me know I will submit it and if there is a documentation note that I am missing please let me know the address. Thank you very much in advance and if this issue was addressed I apologize in advance but do let me know the location of the Document nevertheless. Regards, Rajesh
RE: Renaming directory in repository--questions
Title: RE: Renaming directory in repository--questions When I do log from mmf in my working directory,I see the history before removing it.How do I get the whole history by the cvs log command?Even if I checkout Readme,it still shows only part of the history. Pls help as I am very confused.Did I do anything wrong in moving the file?I followed the manual for this. the way you have done this, you might go back and just change the commit message to something that references the old location and maybe why you decided to move it. i.e.: % cvs admin -m1.2:moved this file from mmf.. = My thoughts: 1) make the new_dir as described from outside repository. 2) in the actual directories on the cvs repository copy concerned ,v files into the new_dir location. Since all files are same (only under a different parent directory )it would also continue to have history at the new location. I tried it on a test repository and it worked, but I am looking for input if it is a good idea to it on the main cvs repository ? I have to do a similar moving but we want all the history and previous versions available at the new location. Rajesh == m -- there are many things in life you can be fashionably late to, but the MGM Grand buffet is not one of them.. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
cvs2cl.pl : Create Changelog Report
Title: cvs2cl.pl : Create Changelog Report Hi, I am trying to generate a Changelog with cvs2cl.pl. My problem is I am not able to get the desired output, which is : a list of files that had changes done to them between revision tags say rel_1 and rel_2. ( Both the revision tags exist for the the files as seen by : cvs status -v : command). I tried to use the command cvs2cl.pl -l -rrel_1 -rrel_2. Thank you very much for your time and help. Regards, Rajesh
