Fix for #11, Added Support for Custom Destination Names #16
Conversation
This file contains 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
added 2 commits
April 3, 2012 18:49
…ory to support fixed revisions at custom destinations
…on-whitespace characters and made the separator match any type of whitespace
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
the script did not work for me as is because for whatever reason
git svn show-externalsdid not separate the revision and the path in my setting.In addition, my externals specified a customized name so this needed a little tweaking, too.
Both changes are actually contained within the first commit, but the regexp will fail for directory names that end in a non-ASCII-character.
This is rectified in the second commit which uses the (non-)whitespace-character-distinction to capture the path and revision.