#870882 (Bug #72411) ** 'p4 admin journal' and 'p4d -jj' could incorrectly rotate the server's journal on a heavily loaded Linux server, resulting in some journal records which were generated after the journal rotation being written to the end of the already-rotated journal.
#850073 (Bug #72842) ** 'p4 submit' will no longer record revisions with invalid archive paths after unshelving an integrated file through a branch view.
#815299 (Bug #71661) ** 'p4 reconcile -n' will no longer take an exclusive lock. In a distributed environment this could cause orphaned exclusive locks. This has been fixed.
#811622 (Bug #71819) ** 'p4d -xf 71819' may now be used to clear invalid or unnecessary charset values from the database. Note that this will scan the entire revision table.
#811455 (Bug #71765) ** 'p4 reopen' will no longer set a charset on a non-Unicode file.
#799439 (Bug #71686) ** 'Accept theirs' charset resolves from revisions with corrupt charset values will no longer cause a crash.
#798198 (Bug #71648) ** A case in which a file with multiple sequential deleted revisions could require integration unnecessarily has been fixed.
#782116 (Bug #71155) ** 'p4d -xx db.working db.have' could create spurious delete records for db.working if a file opened for edit is subsequently moved and submitted by another client and the opened file is then synced to the head revision.
#781809 (Bug #70845, #70906) ** Some merge cases involving files being moved, deleted, and readded in unusual ways are now handled better.
#777730 (Bug #70950) ** A 'p4 revert' command which ran concurrently while a 'p4 shelve' command was underway using the same workspace and changelist could cause that shelve command to crash, if the shelve command included certain undocumented arguments.