Hi Greg, Summary: I understand your opinion, I do not share it. :-) [Regarding the facts, I may have mis-remembered them concerning the genesis of the CVS_SERVER environment variable. Greg could be c
Thanks to those who wrote with advice for me. As it turned out, the problem was (apparently) something nobody had thought of, but your suggestions helped me diagnose the problem. As a token of my gra
That would seem to indicate that you are not able to reproduce the conditions that Chris Cameron is observing in the wild rather than that cvs does not have a potential environment variable book kee
RE: VSS: Actually, in VSS you can remove the exclusive lock feature so multiple check outs are possible. As VSS Admin, choose (Tools | Options | General tab = "Allow multiple checkouts"). As for VSS
I'm assuming that by VSS you mean Visual Source Safe. There are some important differences between the two... 1. File Locking (or lack of it) In SourceSafe, when you check out a file, you are the on
I've been working to learn SSL, and I created a CVS pserver-like access method that runs over SSL. I called it sserver. This avoids sending plaintext passwords and data between the client and server,
I see a difference between handing out a shell account that has write access to the repository directory structure and someone cracking pserver to give them a shell with such access. With pserver I h
I think many users want to avoid, rather than prevent, write access. It takes much more effort to prevent inadvertent repo writes. IMHO, it's worth some effort, but not everyone agrees on how much.
To try and keep our repository in order, we have conventions for directory structure eg. company_name/project_name. If a project is imported incorrectly, it will need to be backed out then recommitte
[ On Wednesday, July 25, 2001 at 12:18:14 (-0700), Mark wrote: ] Well then I'm sorry, but you don't have any such assurance now that people can't mess directly with the repository files with cvspserv
[ On Wednesday, July 25, 2001 at 15:08:20 (-0400), Larry Jones wrote: ] Sshd, ftpd, etc., are all widely used *security* programs that are specifically examined day in and day out by security experts
You could say the same thing about sshd, ftpd, etc. Why pick on CVS? In my experience, none of the standard server daemons do that; they just fork. (Well, that's not quite true: daemons that provide
Hi Jonathan, I thought about the situation that you just started with your first project in a new repository. Than you can remove the whole repository and restart. Do you mean with "naming convention
user. Let's not start a philosophical discussion on what "reality" is. I had thought that we already agrred that you will keep your "correct" version of CVS (and name it NCVS) and we would keep our
[ On Tuesday, July 24, 2001 at 14:27:07 (-0400), Noel L Yap wrote: ] How backwards your logic is, Noel. "Popular demand" often (mostly?) has nothing to do with reality. You can't change the reality o
I am more a perl programmer than a shell programmer but if it is possible for perl to report all files and their respective revisions a shell script should be able to do the same. I assume that all p
Hi, I have modified the log.pl script (I think a common script used by CVS users, and referenced by the book of Karl Vogel) to change it in a lotag.pl. So, with this script, I get all the files and t
[ On Friday, July 13, 2001 at 14:20:07 (-0500), Cameron, Steve wrote: ] OK, so what's the problem with using "-L" (and "-I" if necessary) to simply point at the right version of that code (and header
Take a look through Karl Fogel's book for some excellent coverage on repository management <http://cvsbook.red-bean.com/> I would use the current trunk for your 'beta', and simply tag the tree when y
Hi Irina, Perhaps it could be a good idea to have a look at this. http://cvsbook.red-bean.com/cvsbook.html#Getting_Snapshots__Dates_And_Tagging_ You surely will understand why sticky tags are, and ho