Is `@=n` revision specifier the same as `@n,n` in Perforce file specifications? -
is @=n
syntax identical @n,n
syntax?
for example, is
p4 integ //someotherbranch/...@12345,12345 ...
identical to
p4 integ //someotherbranch/...@=12345 ...
?
to access shelved revisions need utilize "@=n" syntax specifically, handled special case changelists shelved files. otherwise end beingness same.
if want technical "@n,n" syntactic sugar "@>=n,@<=n", logically going match same set of depot revisions "@=n" (except shelve special case, involves revisions aren't committed depot yet).
perforce
No comments:
Post a Comment