|#1||12045||brettb||Branching into my area for specific changes needed by us, so that i can keep merging in fixes|
Updated doc to refer to new change map option.
Clarify P4Python requirements (and thus Python 2.7 or 3.3+).
|#4||11234||robert_cowham||Implement configurable change descriptions|
Latest changes by Robert.
Added new options:
--repeat for continuous operation
--sample-config to produce sample config
-Improved logging and notification options (via emails if configured)
-Retries in case of error.
Added the ability to remove +k from the target
Currently tested for add, need to test for edit and integrate as well
invoked by using option -k or --nokeywords
Branched PerforceTransfer from private area to perforce_software
This tool will now get back its original name P4Transfer.
|#1||7986||sven_erik_knop||Changed P4Transfer to PerforceTransfer to conform with naming convention.|
Updated P4Transfer to deal with merge w/ edit integrations.
All types of integrations should now be supported.
Also updated the documentation.
Changed master and local to server1 and server2.
Also added first draft of a documentation that should serve pretty much as the
blog post I intend to write on this tool.