Migrating and updating the project plan from Perforce#171
Open
Migrating and updating the project plan from Perforce#171
Conversation
…an into the Git MPS tree Copied from Perforce Change: 199022
Copied from Perforce Change: 199026
Member
Author
|
Version 1.117 plan wasn't recorded. It would not be correct to retrospectively "plan" it, unless we can uncover a plan that was made at the time. @gareth-rees might have some record elsewhere. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This branch migrates the MPS project plan from Perforce to Git.
Working on #95 .
Solving #125 (comment) .