Re: Deleting a branch....
You sent this to me privately. Please don't do that - if you had sent it to the list, someone else might have replied by now. Gurpreet Singh (SCM) wrote: Thanks Max. Then can we regulate the branch to be created or not... like can we define priveleges who can create the branch/tag ? How can we put check on it. There are 3 possibilities: 1) It may be sufficient that anyone who can commit, can branch. If so, a readers or writers file should suffice. 2) Use the hook scripts in CVSROOT to control access. IIRC, there is a cvs_acls included in the distro. 3) Corey Minyard's ACL patch. NB: I have never used any of these myself, so consider this as a pointer to further research. Max. -Original Message- From: Max Bowsher [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2003 9:55 PM To: Gurpreet Singh (SCM); [EMAIL PROTECTED] Subject: Re: Deleting a branch Gurpreet Singh (SCM) wrote: Hi All This is regarding deleting a branch, thus created on a Module. Is there any specific method / decription in doing it so ? Well I tried to untag it ^ with the following command cvs rtag -d BranchName ModuleName Is this the only way to do so..? Moreover, All the subfolders were not untagged / say deletion of branch completely... ? Deleting a branch is not usually a good idea. Simply untagging (rtag -d) saves virtually no space in the repository, because all the revisions remain there, but they are now anonymous and inaccessible except by revision number on an individual file basis. So, basically, don't delete branches. Max. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Deleting a branch....
Thanx Max. Well just Replied to the Mail.. agreed - should have been To All. Regards ^^ Gurpreet S -Original Message- From: Max Bowsher [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2003 7:05 PM To: Gurpreet Singh (SCM); [EMAIL PROTECTED] Subject: Re: Deleting a branch You sent this to me privately. Please don't do that - if you had sent it to the list, someone else might have replied by now. Gurpreet Singh (SCM) wrote: Thanks Max. Then can we regulate the branch to be created or not... like can we define priveleges who can create the branch/tag ? How can we put check on it. There are 3 possibilities: 1) It may be sufficient that anyone who can commit, can branch. If so, a readers or writers file should suffice. 2) Use the hook scripts in CVSROOT to control access. IIRC, there is a cvs_acls included in the distro. 3) Corey Minyard's ACL patch. NB: I have never used any of these myself, so consider this as a pointer to further research. Max. -Original Message- From: Max Bowsher [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2003 9:55 PM To: Gurpreet Singh (SCM); [EMAIL PROTECTED] Subject: Re: Deleting a branch Gurpreet Singh (SCM) wrote: Hi All This is regarding deleting a branch, thus created on a Module. Is there any specific method / decription in doing it so ? Well I tried to untag it ^ with the following command cvs rtag -d BranchName ModuleName Is this the only way to do so..? Moreover, All the subfolders were not untagged / say deletion of branch completely... ? Deleting a branch is not usually a good idea. Simply untagging (rtag -d) saves virtually no space in the repository, because all the revisions remain there, but they are now anonymous and inaccessible except by revision number on an individual file basis. So, basically, don't delete branches. Max. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
slightly off topic - Directory Structures
Can someone please post a directory structor template for CVS ... This is what I cam up with and just wondering what everyone else does This document will serve as the standard format for projects being entered into CVS. Java Directory Structure under CVS Project Name/src Project Name/build empty directories only Project Name/lib Project Name/config Project Name/Common Project Name/docs Project Name/test Project Name/src ? This is where the source for this project lives. There may be multiple code bases for source. There may be Java, C++, Perl, ksh, cobol all part of one project. The source directory will house all of the source code for the project. The breakdown of this directory will be by code type: Project Name/src/java -This is for any Java code. This is also where the build.xml document lives Project Name/src/C++- This is for C++ code ? This is where the C++ MakeFile lives. Project Name/src/Cobol ? This is for COBOL code - This is where he COBOL MakeFile lives. Project Name/src/scripts ? This is for scripts such as perl, ksh Project Name/build ? This is where code get built. The base of this directory should mirror src. This should only be written to by make or make substitute ( i.e. ant ) These files should not get checked in. Only the directory stubs should be check in Project Name/build/java - This is for any Java code. Project Name/build/C++ -This is for C++ code Project Name/build/Cobol ? This is for COBOL code Project Name/build/scripts ? This is for scripts such as perl, ksh Project Name/lib ? This is where any libraries or external dependencies that are needed for this project are stored. Project Name/lib/java - This is for any Java code. Project Name/lib/C++ -This is for C++ code Project Name/lib/Cobol ? This is for COBOL code Project Name/lib/scripts ? This is for scripts such as perl, ksh Project Name/config ? This is where any configuration files are stored. Project Name/Common ? This is a link to the Common Project. This link is provided as a convenience when doing development. This directory should only be used in development and not in production Project Name/docs ? All Documentation for the Project Project Name/test ? an area for any test scripts or anything related to testing this project ** The information contained herein is confidential and is intended solely for the addresse(s). It shall not be construed as a recommendation to buy or sell any security. Any unauthorized access, use, reproduction, disclosure or dissemination is prohibited. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall assume any legal liability or responsibility for any incorrect, misleading or altered information contained herein. ** ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Setting up CVS
Alright, thank you very much, I'll see if I can't get it up and running off this machine, if not I may try and talk them setting up a 2k/NT machine or a Linux box... Either way I've learned a lot and I may be back to ask more questions soon. Thanks again. -Kristopher G. Hollingsworth --- Fabian Cenedese [EMAIL PROTECTED] wrote: If possible use a WinNT+ machine as server so you can use cvsNT as service. (or even a linux machine, doesn't have to be powerful :) If not available you need to have a shared drive. cvs can cause problems on that, read in the mailing archives. But as you're Windows only it might work well. Then you need a client, be it the pure command line cvs or some GUI like WinCVS. After setting up the repository (on command line with simple 'cvs init S:\RepoPath' (S like shared drive, RepoPath what you like but preferably without spaces) you can continue with adding/importing/ checkouting :) /committing etc... bye Fabi ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs _ Free email at www.Z6.com ( and home of worldmap.com) _ Select your own custom email address for FREE! Get [EMAIL PROTECTED] w/No Ads, 6MB, POP more! http://www.everyone.net/selectmail?campaign=tag ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
how to handle the host.allow file?
Please help me. I set my cvs server in inetd.config like this: cvsserver stream tcp nowait root /usr/sbin/tcpd /usr/bin/cvs -f --allow-root=/home/cvsroot pserver now I can use it in local network, but get a error message when I use it from outside via internet, I think the problem maybe in host.allow file, now I changed it like this: http-rman:ALL Please tell me , is it correct? Or it is notthe key,then please tell me howI should do? Thanks Shanshui ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: how to handle the host.allow file?
shanshui writes: This is a multi-part message in MIME format. Please do not send MIME and/or HTML encrypted messages to the list. Plain text only, PLEASE! I set my cvs server in inetd.config like this: cvsserver stream tcp nowait root /usr/sbin/tcpd /usr/bin/cvs -f --allow-root=3D/home/cvsroot pserver now I can use it in local network, but get a error message when I use it from outside via internet, I think the problem maybe in host.allow file, now I changed it like this: http-rman:ALL Please tell me , is it correct? We're CVS experts, not tdpd experts. Nonetheless, I don't think that's correct. As I understand tcpd, that says that anyone is allowed to use the http-rman server, whatever that is. I believe you want: cvs: ALL But that prompts the question, why bother running CVS under tcpd if you're not going to restrict access to it? -Larry Jones Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
