14 messages in com.perforce.perforce-user[p4] Multiple Branch Management| From | Sent On | Attachments |
|---|---|---|
| Edward Tsai | 05 Sep 2003 15:16 | |
| Robert Cowham | 08 Sep 2003 03:21 | |
| Bob Arnson | 08 Sep 2003 04:59 | |
| Robert Cowham | 08 Sep 2003 05:33 | |
| Alen Ladavac | 08 Sep 2003 06:37 | |
| Jeff Bowles | 08 Sep 2003 07:03 | |
| Alen Ladavac | 08 Sep 2003 07:09 | |
| Grills, Jeff | 08 Sep 2003 08:21 | |
| Edward Tsai | 08 Sep 2003 10:10 | |
| Alen Ladavac | 08 Sep 2003 10:31 | |
| Jason Williams | 08 Sep 2003 10:37 | |
| Robert Cowham | 08 Sep 2003 10:49 | |
| Stephen Vance | 08 Sep 2003 20:21 | |
| Jeff Bowles | 09 Sep 2003 11:13 |
| Subject: | [p4] Multiple Branch Management |
|---|---|
| From: | Robert Cowham (rob...@vaccaperna.co.uk) |
| Date: | 09/08/2003 03:21:09 AM |
| List: | com.perforce.perforce-user |
Edward
I'm trying to create a tool that manages multiple branch / integrations well... basically lets say i want to create a branch version 5 off of the main line, like
//depot/product/main/latest/...
and get
//depot/product/v5/5.0.0/latest/...
as a branch... it may be the case that I also branch off two other v5s off of v5, like
//depot/product/v5/5.23/latest/... and //depot/product/v5/5.3/latest/... which come from 5.0.0
What I am wondering is if I should manage / keep this information in the "p4 branch" command, such as where i can specify multiple views... it may be the case that I want to make sure that any changes I make to 5.23 also get moved ito 5.3 and also into //depot/product/main/latest/...
I was thinking of keeping a flat file with a "global" view of all branch relationships, where lets say, the user says, 5.23 must "push" all files/keep track of all unintegrated/merged files towards 5.3 and main/latest/...
If I make a front end UI for this, it would mean that if I go to the page that describes 5.23, i would see branches where 5.23 is pulling changes from (perhaps all 5.0 changes) and pushing into (5.3, latest).
How do you keep track of where branch changes need to go?
Not sure if I quite understand your question - given your config file with the global view of branch relationships, do you want to find out which changes need propagating?
Robert