#152382 **
Sometimes 'p4 integrate' would find a distant base when
cherry picking revisions to integrate. Now 'p4 integrate'
insists that the base be the revision before the first
revision being integrated when cherry picking revisions.
(Bug #29016).
#152296 **
'p4 submit' could report "No files to submit" if the
combination of client mapped files and protections table
exceeded an internal limit. This limit was incorrectly
reached on case-insensitive Servers (Windows) by repeated
values in a generated map. This has been fixed. (Bug #28853)
#149704 **
'p4 integrate' could skip integrations in the face of
large branch views coupled with large protection tables.
This has been corrected. (Bug #28659)
#149538 **
'p4 integrate' could report "no permission on file(s)" if
the protections managed by 'p4 protect' had excessive wildcards
(too many ...'s in too many entries). Now 'p4 integrate'
should be no more sensitive than other commands to the number
of wildcards in protections, and in any event should fail
with a more appropriate message ("too may wildcards").
(Bug #28422).
Changes: http://www.perforce.com/perforce/doc.073/user/relnotes.txt
Bugs fixed: (from release notes):
#136755 **
A perforce server could shutdown with the message
"License expired" even when a new license with a valid
expire date was put in place (either manually or with
the 'p4 license' command). This only happened if the
license that the server was originally started with
became out of date. (Bug #24800)
#136742 **
'p4 obliterate' under certain conditions could purge an
archive file which still had lazy copies pointing to it.
This change prevents that from happening. (Bug #26682).
#136586 **
In certain cases inconsistent results depending on depot
path could be observed for some commands. Typically when
this happened an unrestricted 'p4 sync' would bring back
correct behaviour. This problem only occured when a file
that had been previously synced was no longer mapped by the
current client view and the client path name had a '.' in
a significant position of its path. This has been fixed
(Bug #24943, #26541).
#135236 **
Unintegrated revisions prior to a delete could cause
undesirable file re-branching in subsequent integrations.
This change brings back an older behavior, which is to
not re-branch from revisions prior to a delete when the
target is also deleted. (Bug #25662)
For complete list of changes, see:
http://www.perforce.com/perforce/doc.062/user/relnotes.txt
Bugs fixed: (from release notes):
#129932 **
'p4 submit' could fail when 'p4 integrate' mistakenly
attempts to branch from a deleted revision if that
source file was readded and that readded revision was
ignored into the target file. Fixed. (Bug #24663)
#128837 **
The server no longer exits after 10 consecutive attempts
to accept an incoming connection. Usually the reason for
this is that the computer is under configured and its
simply a server resource problem. In some cases the
problem can be on the client end, because of this the
server now sleeps, then continues to retry. (Bug #24156).
For complete list of changes, see:
http://www.perforce.com/perforce/doc.061/user/relnotes.txt
Noticed by: pavmail
