[p4] Strategy for tracking 3rd-party packages
mats.nilsson at xware.se
Thu Jan 15 06:31:08 PST 2004
> That is the way perforce works since the branches are not
> directly related
> to each other (happy to go into more details if required).
If you don't mind, please. But I'd guess this has to do with avoiding
repeated merge problems.
I've skimmed through the documentation, but all I see about "p4
integrate -I" is sweeping statements such as
... "this allows p4 integrate to deal with files where the source
target files are not directly related by branching."
If you have additional pointers to docs with more substantial
information, I'd be very grateful.
> Using -i is not a
> big issue (especially with the new release 2003.2), and
> should be set up in
> the branch spec you use for these things to use indirect
> branching for that
So p4 integrate -i equals "enable baseless", while -I is not accessible
Good to know ;-/
More information about the perforce-user