4 messages in com.perforce.perforce-user[p4] Versioning collections| From | Sent On | Attachments |
|---|---|---|
| Simon De Groot | 25 Jul 2003 05:36 | |
| Paul Goffin | 25 Jul 2003 05:59 | |
| Dave Hildebrandt | 29 Jul 2003 12:07 | |
| Robert Cowham | 29 Jul 2003 13:14 |
| Subject: | [p4] Versioning collections![]() |
|---|---|
| From: | Paul Goffin (Paul...@aepsystems.com) |
| Date: | 07/25/2003 05:59:25 AM |
| List: | com.perforce.perforce-user |
If you wish the changes to two files to be associated, submit them both at the same time.
Perforce considers "changelists" (sets of files submitted together) to be atomic.
Paul.
-----Original Message----- From: perf...@perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Simon De Groot Sent: 25 July 2003 13:37 To: perforce-user at perforce.com Subject: [p4] Versioning collections
Hi all,
I was just wondering, does Perforce support versioning of collections in any way? Say two files file_a and file_b together represent a single design object in some tool. Both of them have latest version 1.x. If I change and submit file_a followed by file_b these two files will both have latest version 1.x+1 now. However my design object will have 1.y+2. How does cdsp4 handle this w.r.t. objects such as Views?
Simon de Groot, CAD Engineer.
.
******************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the postmaster at the address below. ITS-Support at aepsystems.com This footnote also confirms that this email message has been checked for the presence of computer viruses. **********************************************************************




