[p4] branchspec reversed or not?

Russell C. Jackson rusty at rcjacksonconsulting.com
Tue Dec 20 12:47:29 PST 2005


I am only guessing since I didn't write the book, but maybe she is assuming
that most integrations will be from the branch back to the main line, and
setting up the branch view that way makes it possible to do that without
have to check the reverse integration box. Functionally, it doesn't make any
difference, but this seems like a logical reason she may have done that. 

Thanks, 
Rusty
-------------------------------------------------------- 
RCJackson Consulting
Perforce Consulting Partner and Certified Trainer
--------------------------------------------------------
Russell C. Jackson 
211 River Oaks Lane
Russellville, AR 72802
-------------------------------------------------------- 
rusty at rcjacksonconsulting.com 
http://public.perforce.com/guest/russell_jackson/pcp.html 
tel: 479-696-9710
fax: 479-967-2308
mobile: 479-747-3845
-------------------------------------------------------- 

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Dan Halbert
Sent: Tuesday, December 20, 2005 11:34 AM
To: Perforce-User List
Subject: [p4] branchspec reversed or not?

We are about to do our first major branch in Perforce. I read the Perforce
technote NOTE004, which explains things quite clearly. We are branching from
"main" to "v2.0". I can set up a branch spec, called, say, "main-v2.0" with
a view with lines that look like:

    //depot/ourcode/subproject/main/...    
//depot/ourcode/subproject/v2.0/...

However, I also have a copy of Laura Wingerd's new book, Practical Perforce.
She calls branch specs "branch views", and her examples are all set up in
reverse. She might have a branch spec named "v2.0-main", with view lines
like:

    //depot/ourcode/subproject/v2.0/...    
//depot/ourcode/subproject/main/...

She would do "p4 integ -r -b v2.0-main" in order to handle this reversal.

So, now I'm confused. It seems as if she's introducing a new "Better/Best
Practices in Perforce" suggestion. She prefers the reversed branchspecs, but
doesn't really say why that I can see. I'd like to the "best thing" going
forward. It doesn't really matter so much in this case, but can anyone
suggestion what her motivation is here?

Dan
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user






More information about the perforce-user mailing list