|
Size: 3513
Comment:
|
Size: 335
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Perfarce Extension == '''This extension is not distributed with Mercurial.''' ''Author: Frank Kingswood'' Public repository: http://www.kingswood-consulting.co.uk/hg/perfarce === Overview === This extension modifies the remote repository handling so that repository paths that resemble p4://p4server[:port]/clientname cause operations on the named p4 client specification on the p4 server. The client specification must already exist on the server before using this extension. Making changes to the client specification Views causes problems when synchronizing the repositories, and should be avoided. === Commands === outgoing If the destination repository name starts with p4:// then this reports files affected by the revision(s) that are in the local repository but not in the p4 depot. push If the destination repository name starts with p4:// then this exports changes from the local repository to the p4 depot. If no revision is specified then all changes since the last p4 changelist are pushed. In either case, all revisions to be pushed are folded into a single p4 changelist. Optionally the resulting changelist is submitted to the p4 server, controlled by the --submit option to push, or by setting --config perfarce.submit=True If the option --config perfarce.keep=False is False then after a successful submit the files in the p4 workarea will be deleted. pull If the source repository name starts with p4:// then this imports changes from the p4 depot, automatically creating merges of changelists submitted by hg push. If the option --config perfarce.keep=False is False then the import does not leave files in the p4 workarea, otherwise the p4 workarea will be updated with the new files. The option --config perfarce.clientuser=search replace can be used to enable quasi-multiuser operation, where several users submit changes to p4 with the same user name and have their real user name in the p4 client spec. The search and replace regular expressions describe the substitution to be made to turn a client spec name into a user name. If the search regex does not match then the username is left unchanged. incoming If the source repository name starts with p4:// then this reports changes in the p4 depot that are not yet in the local repository. clone If the source repository name starts with p4:// then this creates the destination repository and pulls all changes from the p4 depot into it. If the option --config perfarce.lowercasepaths=False is True then the import forces all paths in lowercase, otherwise paths are recorded unchanged. Filename case is always preserved. This setting is a workaround to handle Perforce depots containing a path spelled differently from file to file (e.g. path/foo and PAth/bar). === Configuration === Configure your .hgrc to enable the extension by adding following lines: {{{ [extensions] perfarce = /path/to/perfarce.py }}} ---- CategoryExtensionsByOthers |
24 year old Swimming Coach or Instructor Forrest from Charlottetown, has hobbies and interests such as gardening, [[http://www.mknet360.com/wiki/index.php/Training_History_With_Classroom_Games|Icomania Answers]] and chess. Will shortly undertake a contiki journey that may cover planing a trip to the Margravial Opera House Bayreuth. |
24 year old Swimming Coach or Instructor Forrest from Charlottetown, has hobbies and interests such as gardening, Icomania Answers and chess. Will shortly undertake a contiki journey that may cover planing a trip to the Margravial Opera House Bayreuth.