1) Install 'p4' into your HOME/bin directory (assuming that is in your PATH) 2) Edit 'p4' to specify your platform if different from darwin90x86_64, see ftp.perforce.com/perforce/r14.1 for possible platforms 3) Make 'p4' executable: chmod a+x $HOME/p4 4) Check to make sure this is the 'p4' that you're using: which p4 Available commands: p4 init {directory} Create a Perforce storage structure in the current or specified sub-directory When in a Perforce storage structure: p4 switch p4 newbranch BRANCHNAME Create a branch of the given name and switch to it p4 switch BRANCHNAME Switch to the named branch p4 mergefrom BRANCHNAME Run integ from BRANCHNAME into CURBRANCH if a branch named 'merge-BRANCH1-BRANCH2' exists that matches these two then the integ will use as the args, o/w it will use //branch/BRANCH1/... and //branch/BRANCH2 When switching branches, check for pending work and give you options for how to resolve the issues. Note: track-remotes.sh is just useful for working with Git
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#10 | 11576 | Alan H Teague |
Closing off the myp4 project as pre-2015.1 Perforce Providing reference to the myb4 project as the future |
||
#9 | 9724 | Alan H Teague | Clean up help | ||
#8 | 9700 | Alan H Teague | Adding in p4 check command | ||
#7 | 9030 | Alan H Teague | Update for changes to switch/branch | ||
#6 | 8862 | Alan H Teague | Update some odds and ends | ||
#5 | 8807 | Alan H Teague | Update README | ||
#4 | 8802 | Alan H Teague | Update to add mergedown | ||
#3 | 8778 | Alan H Teague | Make it work with both basic p4 and wrapped p4 | ||
#2 | 8776 | Alan H Teague | Remove indirection of branch names | ||
#1 | 8774 | Alan H Teague | Initial import of the myp4 project |