diff options
author | lth <lth@FreeBSD.org> | 2007-10-19 15:54:00 +0800 |
---|---|---|
committer | lth <lth@FreeBSD.org> | 2007-10-19 15:54:00 +0800 |
commit | 5d5f666e24b502359f3f27e93c5cb31993b12659 (patch) | |
tree | 58b9c0b4833d79560f01b29caac7403809652e13 /games/oilwar | |
parent | 0819daedd77eba103992e8113e7b314a6a17f580 (diff) | |
download | freebsd-ports-gnome-5d5f666e24b502359f3f27e93c5cb31993b12659.tar.gz freebsd-ports-gnome-5d5f666e24b502359f3f27e93c5cb31993b12659.tar.zst freebsd-ports-gnome-5d5f666e24b502359f3f27e93c5cb31993b12659.zip |
Chase updated binaries.
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
Diffstat (limited to 'games/oilwar')
0 files changed, 0 insertions, 0 deletions