[p4] "highest revision" for p4 tag
Kevin.Calman at acs-inc.com
Thu Jan 17 16:24:24 PST 2008
When the CmdRef doc says, "If more than one revision of the file exists in
the specified range, the highest revision in the specified range is
tagged.", is this for real or is it dependant on the order of the specifiers
in the range?
- Changelist 234 contains file //depot/foo#2
- Label "base" contains file //depot/foo#5
"p4 tag -l new //... at 234, at base"
should be equivalent to
"p4 tag -l new //.../foo#>=2,foo#<=5"
and make label "new" contain foo#5. But will
"p4 tag -l new //... at base, at 234"
which should be equivalent to
"p4 tag -l new //.../foo#>=5,foo#<=2"
do the same thing? Is there a way to specify the range to avoid this
What if changelist 234 contains file //depot/foo#2 and
//depot/bar#1, does bar get tagged into the label "new" in the cases above?
What if 'p4 labelsync' is used instead of 'p4 tag'?
Opinions herein are exclusively my own, unless you share them.
Kevin Calman, ACS Inc, Austin TX US
More information about the perforce-user