2 messages in com.perforce.perforce-user[p4] Maintaining patches| From | Sent On | Attachments |
|---|---|---|
| Carsten Orthbandt | 07 Aug 2002 11:39 | |
| Cubbage, Jim | 07 Aug 2002 14:12 |
| Subject: | [p4] Maintaining patches |
|---|---|
| From: | Cubbage, Jim (jcub...@SiliconEnergy.com) |
| Date: | 08/07/2002 02:12:04 PM |
| List: | com.perforce.perforce-user |
I am new to perforce, but if I were to do that I would probably use a label. It is the way I would have done it in VSS or any other source control. You could track the change number I hear, but a label allows you to add specific versions of specific files if you have to do an update between updates. Now you can do a diff between labels if you want. There may be other ways to do the same thing in Perfoce and I am sure someone will answer soon.
-----Original Message----- From: Carsten Orthbandt [mailto:carsten.orthbandt at sek-ost.de] Sent: Wednesday, August 07, 2002 11:40 AM To: perforce-user at perforce.com Subject: [p4] Maintaining patches
Hi! I'd just like to be sure I'm on the right track here. We have a local P4 server with a special depot with all files our publisher should have. From time to time I'd like to build a single-file patch against the last known snapshot. This file I transfer to our publisher, they run it on their mirror of our depot et voila, current data at their site. Doing the patch is already solved. But for building the patch I need two snapshots. Our current status of the depot (easy) and the last known state of our publishers server. I could easily copy the whole tree over from my depot client view after building a new patch or even simply apply the patch to that "old" directory myself. But I'd like to keep that data in Perforce, too. What I don't want is having all that redundant data physically stored in our server since it is already in the history of the current snapshot depot. My idea is to use branching and doing an p4 integrate //pub_current_data/... //pub_last_snapshot/... and have only "softlinks" in the database, not actual copies of all that stuff in //pub_last_snapshot. Will that work or do I have to live with duplicates of the files?
--- Carsten Orthbandt, Director Development SEK SpieleEntwicklungsKombinat GmbH http://www.sek-ost.de
"Wenn ich Visionen habe, gehe ich zum Arzt." - Helmut Schmidt
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user