16 messages in com.perforce.perforce-userDependent Project handling?
FromSent OnAttachments
Robe...@SCRAP.de28 May 1998 05:54 
Ines...@llnl.gov28 May 1998 07:44 
Robe...@SCRAP.de28 May 1998 09:39 
Davi...@home.chat.net28 May 1998 10:59 
Davi...@home.chat.net28 May 1998 11:09 
Davi...@home.chat.net28 May 1998 11:23 
Davi...@home.chat.net28 May 1998 11:37 
Robe...@SCRAP.de28 May 1998 23:41 
Davi...@home.chat.net29 May 1998 02:39 
Davi...@home.chat.net29 May 1998 02:57 
Robe...@SCRAP.de29 May 1998 03:36 
Robe...@SCRAP.de29 May 1998 03:39 
Robe...@SCRAP.de29 May 1998 03:42 
Davi...@home.chat.net29 May 1998 10:42 
Davi...@home.chat.net29 May 1998 11:06 
Robe...@SCRAP.de29 May 1998 22:23 
Subject:Dependent Project handling?
From:Davi...@home.chat.net (Davi@home.chat.net)
Date:05/29/1998 02:39:33 AM
List:com.perforce.perforce-user

On Thu, May 28, 1998 at 06:40:20PM +0200, Robert M. M=FCnch wrote:

I think I have to use a branch here, for virtually coping the files of proj1 into proj2. Can a branch be made from a label? Is there something like an auto-update branch available, that resync to the files of proj1 if the label of proj1 has been changed/updated?

I also think this is the best choice. It preserves the most information. Yes, a branch can be made from a label. A label is just like a changelist in that it specifies a set of files and their associated revisions.

There is no such thing as an auto-update branch. Perforce implements mechanism, not policy. So if you want an auto-update branch, you'll have to use some sort of change-review daemon and have it perform the required automatic policy.

---=20 David Jeske (N9LCA) + http://www.chat.net/~jeske/ + jeske at chat.net