3 messages in com.perforce.perforce-user[p4] Re: perforce-user digest, Vol 1 ...
FromSent OnAttachments
Patrick Moore11 Oct 1999 13:27 
Dave Birkhead11 Oct 1999 13:45 
Stephen Vance13 Oct 1999 05:02 
Subject:[p4] Re: perforce-user digest, Vol 1 #63 - 1 msg
From:Stephen Vance (ste@vance.com)
Date:10/13/1999 05:02:32 AM
List:com.perforce.perforce-user

Additionally, it's slow, requires file system access for networked use, only practically works with one sandbox on a machine, and doesn't have any better branching model than RCS.

Dave Birkhead wrote:

I agree with Patrick, Although our problem was around Source Integrity getting confused about which branch it was working on. Sometimes it would return the head revision of a file FROM THE WRONG BRANCH!

-----Original Message----- From: Patrick Moore [mailto:patrickm at manage.com] Sent: Monday, October 11, 1999 13:28 PM To: perforce-user at perforce.com Subject: [p4] Re: perforce-user digest, Vol 1 #63 - 1 msg

Don't use SourceIntegrity -- many problems -- caused primarily by not being able to have multiple people check out files.

Message: 1 From: Caroline Ghali <Caroline.Ghali at CRAMER.CO.UK> To: "'PERFORCE-USER at PERFORCE.COM'" <PERFORCE-USER at PERFORCE.COM> Date: Mon, 11 Oct 1999 14:23:20 +0100 charset="iso-8859-1" Subject: [p4] (no subject)

Hi,

Has anyone used MKS SourceIntegrity and MKS TrackIntegrity? I'd like some opinions if possible.

Thanks in advance

Caroline Ghali

--__--__--

End of perforce-user Digest

A computer programmer is a machine for turning coffee into programs. -- Paraphrase of the late mathematician Paul Erdo"s