4 messages in com.perforce.perforce-user[p4] Possible to "preview" a major in...| From | Sent On | Attachments |
|---|---|---|
| brya...@autodesk.com | 26 Jul 2000 15:17 | |
| Dave Lewis | 26 Jul 2000 15:28 | |
| Ines Heinz | 26 Jul 2000 16:07 | |
| Jo Woodison | 27 Jul 2000 09:28 |
| Subject: | [p4] Possible to "preview" a major integrate from branch spec ?![]() |
|---|---|
| From: | Ines Heinz (hei...@llnl.gov) |
| Date: | 07/26/2000 04:07:27 PM |
| List: | com.perforce.perforce-user |
The only times we have had problems with this is when the client has already had files open or missing or chmoded to +write. If you do the p4 revert, then you lose whatever changes you were making before you did the integrate.
Ines
bryan.dawson at autodesk.com wrote:
We have a really huge integrate from a branch spec that we want to do. We expect that the integrate will produce a change list containing perhaps 5000 files. Management would like to know the size of this change list, the number of files needing resolved, and the number of files STILL needing resolved after "resolve automatically". They plan to use this data as a guideline for how many person-hours this whole thing might take.
I'm thinking of gathering the information like so:
1) Perform the integrate using branch-spec, this will generate a change list. 2) Gather statistics from the changelist 3) Perform an auto-resolve and gather some more statistics 4) Revert all files in the changelist
I think that no information about the integrates and resolves would actually get stored by Perforce until a submit, so hopefully step (4) would *completely* undo this "preview integrate" so that it can be re-done at a later date.
Does anyone know if the procedure described above will correctly leave the depot in a state where the integrate can be cleanly repeated (and completed) at a later date ???
-- Thanks! Bryan Dawson Autodesk Inc.
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user




