This repository was archived by the owner on Sep 6, 2021. It is now read-only.
Prevent prefix based conflicts when renaming #2914
Merged
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
…though "foo" is a prefix of "foobar".
ghost
assigned
Member
|
Looks good. Thanks! |
gruehle
added a commit
that referenced
this pull request
Feb 26, 2013
Prevent prefix based conflicts when renaming
Contributor
Author
|
Thanks, Glenn! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
Renaming file "foo" should not affect file "foobar/baz" even though "foo" is a prefix of "foobar".
Best merged after #2912 since it can't really be tested without it. Though the commit is included here, too. Please let me know if I should create a pull request with just the last commit.