No, there's only one branching mechanism in Perforce.
There are two ways to access it.
You can either use the "integrate" command directly. Or you
can use it with a branch specification if that suits your
way of working.
What confusion there is is thinking that a branch spec is
anything more than a useful place holder for the _real_
branching command which is confusingly named "integrate".
Paul.
-----Original Message-----
From: Andrew Mulcahy, T-CH [mailto:andrew.mulcahy@xxxxxxxxx]
Sent: 21 July 2004 15:31
To: Bennett, Patrick; perforce-user@xxxxxxxxxxxx
Subject: RE: [p4] Anybody out there evaluated Subversion or MS Visual
Studio Team Foundation?
I admit to being a rather novice Perforce user as I only evaluated it on and
off for a couple of months. However, the fact that there are two types of
branching mechanisms (and gauging by Noel's comment, varying opinion on
which is best) immediately increases the difficulty factor. When I started
using P4 I chose to use the Branch Spec mechanism (possibly a mistake to do
so, though the name "Branch Spec" alludes one to it more readily than "File
Spec") and took me quite while to figure it out. I figured out Subversion
branches in less than 2 minutes, thus I appraised it as being simpler.
Andrew
-----Original Message-----
From: Noel Yap [mailto:Noel.Yap@xxxxxxxxxxxxxxxxx]
Sent: 21 July 2004 16:21
To: Bennett, Patrick
Cc: Andrew Mulcahy, T-CH; Arnt Gulbrandsen;
JeremyRobert.Smith@xxxxxxxxxx; Brad Holt; perforce-user@xxxxxxxxxxxx
Subject: Re: [p4] Anybody out there evaluated Subversion or MS Visual
Studio Team Foundation?
Bennett, Patrick wrote:
> [Bennett, Patrick] So how exactly is Perforce any more difficult? P4
> integ (source_path...) (dest_path...) ? That's about as easy as it
> gets. Branch specs are just a way of defining more complex path
> translations, they're seldom necessary.
IMHO, in addition to convenience for complex path translations, they offer
documentation for the branch and minimize risk of error when integrating (eg
ever mistype the destination?) -- they should almost /always/ be used.
Noel
_______________________________________________
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept for the
presence of computer viruses.
*****************************************************************************
_______________________________________________
perforce-user mailing list - perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user
|
