Re: CVS Pros/Cons

Larry Jones <[EMAIL PROTECTED]> wrote: >> Kevin Layer writes: >> > >> > "Wouldn't be that hard" is an overstatement. To close the harzard >> > completely would be hard, otherwise it would have been done already. >> >> It act

Re: CVS Pros/Cons

Donald Sharp \(sharpd\) <[EMAIL PROTECTED]> wrote: >> >Check-outs and commits are not atomic. The repository >> >will not become corrupt, but if you are checking in a >> >number of files and one file fails, the system does >> >not roll back the other files in the repository to >> >their state befo

Re: Case insensitivity ad nauseum

Jim.Hyslop <[EMAIL PROTECTED]> wrote: >> ... >> is it generally considered >> bad practise to have two files with the same name, that differ only by case, >> in the same directory? Yes. >> My understanding is that the common practise on Unix >> is to use all lower-case names, to avoid potential

Re: symbolically linked module root

Mark D. Baushke <[EMAIL PROTECTED]> wrote: >> Kevin Layer <[EMAIL PROTECTED]> writes: >> >> > I want to give a contractor access to one module in my repository. >> > Let's say I have this situation: >> > >>

symbolically linked module root

repository directory like this: cvsroot2/ CVSROOT -> ../cvsroot/CVSROOT modc -> ../cvsroot/modc and having them use cvsroot2 as their repository. Is this safe? Is there a better way to do what I want to do? Thanks. Kevin Layer ___ In

Re: updated to 1.11.6 (from 1.11.2) now have problems on windows

Eric Siegerman <[EMAIL PROTECTED]> wrote: >> Instead, perhaps it should do something like: "if the specified >> pathname, together with the usual other criteria (-r, -D, sticky >> attributes, etc.), selects more than one *revision*, complain". >> >> The existing (I think) test cares about theoret

Re: updated to 1.11.6 (from 1.11.2) now have problems on windows

Lots of instances of the following in my repository: foo,v Attic/Foo,v where the Attic file was cvs rm'd years ago and is not used anymore. If I rename Attic/Foo,v to Attic/Foo_renamed_due_to_cvs_bug,v and "cvs update -d" on my Windows box, all is well. ___

Re: updated to 1.11.6 (from 1.11.2) now have problems on windows

>> I'm running the cygwin 1.11.5 client on Windows 2k sp4. Btw, upgrading cygwin, which contaains 1.11.6, does not fix the problem. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs

updated to 1.11.6 (from 1.11.2) now have problems on windows

I'm running the cygwin 1.11.5 client on Windows 2k sp4. Got this when I updated today on Windows, after upgrading to 1.11.6 yesterday on the linux RH server (2.4.22 kernel): D:\acl7\src\cl>cvs update -d cvs server: Updating . P ChangeLog cvs update: move away ./Makefile; it is in the way C Makefi

Re: Preventing Commits to a Branch

Alexandre Augusto Drummond Barroso <[EMAIL PROTECTED]> wrote: >> You may create a program to be called on every commit >> operation. Your program must analyze the file names, their >> revision numbers (the third part of revision number identifies >> the branch - the x in 1.1.x.1 identifies the b

Re: -D date_spec and branches

Mark D. Baushke <[EMAIL PROTECTED]> wrote: >> Kevin Layer <[EMAIL PROTECTED]> writes: >> >> > Pardon me for replying my own message, but having seen lots of >> > other mail go by... can someone please take a second and tell me if >> > I'm

Re: -D date_spec and branches

My tests show that your suggestions do not work. I'm using 1.11.2. The revisions are always retrieved from the trunk, not the sticky tag (branch) for the tree I'm in. Øyvind A. Holm <[EMAIL PROTECTED]> wrote: >> On 2003-05-28 15:41-0700 Kevin Layer wrote: >>

Re: -D date_spec and branches

Pardon me for replying my own message, but having seen lots of other mail go by... can someone please take a second and tell me if I'm SOL or if it's possible? Thanks. Kevin Layer wrote: >> How do I reference the revisions on a branch for a specific date? >> >&g

-D date_spec and branches

How do I reference the revisions on a branch for a specific date? cvs diff -D "2 days ago" always seems to refer to the trunk, and not the branch I'm on. I looked at the FAQ on cvshome.org and googled for an hour, without success. IIRC, this is a long standing issue, but I really need the fe

Re: I want recursion, just not into other modules: possible?

ntire process takes 30 minutes, whereas it would take minutes if I didn't have to do the last step. Either I'm using cvs wrong, which I would argue I'm not, or cvs is lacking a feature that will allow me to use it more effectively. >> Kevin Layer writes: >> > >

Re: I want recursion, just not into other modules: possible?

>> Kevin Layer writes (quoting me): >> > >> >> > >> No -- once it's checked out, CVS has no way to know whether two >> > >> different directories came from the same module or not. >> > >> > Well, it could. The inform

Re: I want recursion, just not into other modules: possible?

>> Kevin Layer writes: >> > >> > I normally like the behavior of cvs, going into all modules checked >> > out inside my top-level module. Is there a way to stop this, while >> > still allowing the recursing into directories of the same module? >>

I want recursion, just not into other modules: possible?

I normally like the behavior of cvs, going into all modules checked out inside my top-level module. Is there a way to stop this, while still allowing the recursing into directories of the same module? Kevin Layer ___ Info-cvs mailing list [EMAIL