p4v integration #36
Open
p4v integration #36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull request ericmartel#13: p4v commands added to context menu
This change should get the p4v commands to work in more perforce deployment scenarios. Server license-ip might be a separate host:port depending on your perforce infrastructure.
Open
…of it, if it is set, instead of defaulting to 1667
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes the merge conflict in mattyork's pull request #13 and also fixes the patch so that the p4v commands work in more perforce scenarios.
Tested in an environment which used separate host:ports for the server, peer, broker and server license addresses.