Re: cvs diff - new files

[ On Tuesday, June 17, 2003 at 11:24:26 (+0530), Jayashree wrote: ] Subject: cvs diff - new files I've noticed that cvs diff does not show new files when the export CVSROOT is not using pserver. Any ways by which I can find out new files to be baselined in a folder? How about trying cvs

update -j -j pulls in more than we want

Hello Lately I've been stung when applying update -j -j to wildly disparate versions of a program. CVS insists on pulling in unwanted fixes in order to meet its contextual needs it seems. While this makes sense is there any way of predicting or controlling how cvs behaves in such

checkout/commit onto/from shared disks.

Hi, I'd like to start by thanking everyone for the advice I've received from previous posts...so thank you all. Alas, I once more seek your advice though. I intend to build a clustered linux solution for our developers to use. This would comprise of one central server upon which all the

Re: checkout/commit onto/from shared disks.

what is your concern? The only one that I can see would be large files with frequent changes over a slow network. But even that wouldnt seem like much of an issue. Tom |-+- | | David Bowring

RE: checkout/commit onto/from shared disks.

My concerns were merely that I had heard noises about using CVS on disk shares and was worried (in some part) about corruption, though I could not foresee it. All the clustered machines will be on a Gigabit backbone, so this should negate the network throughput issue. Cheers -Original

Re: checkout/commit onto/from shared disks.

David Bowring wrote: My concerns were merely that I had heard noises about using CVS on disk shares and was worried (in some part) about corruption, though I could not foresee it. All the clustered machines will be on a Gigabit backbone, so this should negate the network throughput issue.

Re: checkout/commit onto/from shared disks.

Max Bowsher wrote: David Bowring wrote: My concerns were merely that I had heard noises about using CVS on disk shares and was worried (in some part) about corruption, though I could not foresee it. All the clustered machines will be on a Gigabit backbone, so this should negate the

Re: checkout/commit onto/from shared disks.

David Bowring writes: My concern is being that each of our developers home directories will be a disk share from the central machine, and all the checkout/commit will be done via pserver onto these shares (I am considering using NFS to create the shares). If anyone can give me any guidance

Re: checkout/commit onto/from shared disks.

Riechers, Matthew W writes: As anecdotal evidence, I'd submit that I have been hosting several sandboxes on NFS shares for years without incident. As long as the path between the client and server is not over a network sharing system, you shouldn't have a problem. NFS mounted working

Re: checkout/commit onto/from shared disks.

[ On Tuesday, June 17, 2003 at 10:27:21 (-0400), Larry Jones wrote: ] Subject: Re: checkout/commit onto/from shared disks. All of the known NFS problems are interoperability problems between different NFS implementations. Well there can also be generic NFS problems between server and client

Re: checkout/commit onto/from shared disks.

[ On Tuesday, June 17, 2003 at 13:03:52 (+0100), David Bowring wrote: ] Subject: checkout/commit onto/from shared disks. This would comprise of one central server upon which all the developers home directories and cvs server would reside. They will be logged into any one of many machines

Re: checkout/commit onto/from shared disks.

Greg A. Woods writes [quoting me]: All of the known NFS problems are interoperability problems between different NFS implementations. Well there can also be generic NFS problems between server and client of the same implementation. For example NetBSD has full support for file locking

Re: checkout/commit onto/from shared disks.

This is more or less what I'm trying to set up, Checkout/commit over a small LAN here. Everything would be over shared drives, but I don't know how to setup the CVSServer, so if someone could point me to some documentation on this or any other help towards that end... The Repository would be

Re: checkout/commit onto/from shared disks.

[ On Tuesday, June 17, 2003 at 11:38:41 (-0700), Kristopher Hollingsworth wrote: ] Subject: Re: checkout/commit onto/from shared disks. This is more or less what I'm trying to set up, Checkout/commit over a small LAN here. Everything would be over shared drives, but I don't know how to

Re: checkout/commit onto/from shared disks.

Yeh... That'd be nice, I'll see what I can't talk them in to doing... Oh well, Thanks for the help, it's appreciated. -Kristopher G. Hollingsworth --- Greg A. Woods [EMAIL PROTECTED] wrote: I think you're in the wrong newsgroup/mailing-list. As far as I know this CVS doesn't run

RE: checkout/commit onto/from shared disks.

Greg, I have recently rejoined the CVS community and have come to the conclusion that you are one of the most unhelpful people on the list. You sound like a throw back to 10 or more years ago when the net was free and attitudes like yours flourished. Bert -Original Message- From: Greg