job000217
Closed
Perforce labels spanning branches
I'm using Convert mode and converting labels and branches. As it stands, the labels are applied to various branch versions. For example:
$ p4 -p 1666 files @IPX_C19
//depot/icm/proj/USB30phy/BCG_28NM/rtl/rtl/files.f#5 - integrate change 247907 (ltext)
//depot/icm/proj/USB30phy/BCG_28NM/rtl/rtl/usb30_core2dfe.sv#7 - integrate change 247935 (text+Fx)
//depot/icm/proj/USB30phy/BCG_28NM/rtl/rtl/usb30_dfe.sv#8 - integrate change 247982 (text+Fx)
...
//depot/icm/proj/USB30phy/BCM63381_A0/rtl/rtl/usb30_phy.sv#8 - integrate change 247971 (text+Fx)
//depot/icm/proj/USB30phy/BCM63381_A0/rtl/rtl/usb30_rxpmd_clk_gen.sv#2 - integrate change 247858 (ltext)
//depot/icm/proj/USB30phy/BCM63381_A0/rtl/rtl/usb30_txpmd_clk_gen.sv#2 - integrate change 247859 (ltext)
...
//depot/icm/proj/USB30phy/main/rtl/rtl/usb30_mdio_creg.sv#1 - import change 247738 (ltext)
//depot/icm/proj/USB30phy/main/rtl/rtl/usb30_mdio_csreg_5.v#2 - integrate change 247439 (text+Fx)
//depot/icm/proj/USB30phy/main/rtl/rtl/usb30_mdio_csreg_8.v#2 - integrate change 247439 (text+Fx)
All these files reside in the same directory in the tree - only differing because of the branch directory. Since these labels are applied on different branches, I cannot 'sync' to a label and pick up the entire fileset in one place.
In CVS I would be able to run 'cvs get -r <label> <module>' and end up with all files tagged with that particular label - no matter the branch.
During conversion, would it make more sense to apply the label to all the files on a particular branch so they're all visible?
I'm using Convert mode and converting labels and branches. As it stands, the labels are applied to various branch versions. For example:
$ p4 -p 1666 files @IPX_C19
//depot/icm/proj/USB30phy/BCG_28NM/rtl/rtl/files.f#5 - integrate change 247907 (ltext)
//depot/icm/proj/USB30phy/BCG_28NM/rtl/rtl/usb30_core2dfe.sv#7 - integrate change 247935 (text+Fx)
//depot/icm/proj/USB30phy/BCG_28NM/rtl/rtl/usb30_dfe.sv#8 - integrate change 247982 (text+Fx)
...
//depot/icm/proj/USB30phy/BCM63381_A0/rtl/rtl/usb30_phy.sv#8 - integrate change 247971 (text+Fx)
//depot/icm/proj/USB30phy/BCM63381_A0/rtl/rtl/usb30_rxpmd_clk_gen.sv#2 - integrate change 247858 (ltext)
//depot/icm/proj/USB30phy/BCM63381_A0/rtl/rtl/usb30_txpmd_clk_gen.sv#2 - integrate change 247859 (ltext)
...
//depot/icm/proj/USB30phy/main/rtl/rtl/usb30_mdio_creg.sv#1 - import change 247738 (ltext)
//depot/icm/proj/USB30phy/main/rtl/rtl/usb30_mdio_csreg_5.v#2 - integrate change 247439 (text+Fx)
//depot/icm/proj/USB30phy/main/rtl/rtl/usb30_mdio_csreg_8.v#2 - integrate change 247439 (text+Fx)
All these files reside in the same directory in the tree - only differing because of the branch directory. Since these labels are applied on different branches, I cannot 'sync' to a label and pick up the entire fileset in one place.
In CVS I would be able to run 'cvs get -r <label> <module>' and end up with all files tagged with that particular label - no matter the branch.
During conversion, would it make more sense to apply the label to all the files on a particular branch so they're all visible?
- Status
- Closed
- Project
- perforce-software-p4convert
- Severity
- C
- Reported By
- ddvalk
- Reported Date
- 10 years ago
- Modified By
- Perforce maintenance
- Modified Date
- 6 years ago
- Owned By
- ddvalk
- Type
- Bug
If the label 'IPX_C19' spans multiple branches and you wanted just branch 'BCG_28NM' then
p4 sync //depot/icm/proj/USB30phy/BCG_28NM/...@IPX_C19
However, to flatten the three directories above (assuming that they contain unique files) you would need a workspace with overlay ('+') mapping. http://www.perforce.com/perforce/r15.1/manuals/cmdref/views.html
//depot/icm/proj/USB30phy/main/... //my_workspace/...
+//depot/icm/proj/USB30phy/BCG_28NM/... //my_workspace/...
+//depot/icm/proj/USB30phy/BCM63381_A0/... //my_workspace/...
then,
p4 sync //my_workspace/...@IPX_C19
Thanks for the tip/schooling. I'll look into this.