Prepare for packaging#4
Closed
rubo wants to merge 18 commits into
Closed
Conversation
|
shouldn't we bring these changes in two PRs? |
Collaborator
Author
|
@tanishqjasoria I don't see any necessity of splitting it into multiple PR's. It's a rebase. |
Added try-catch block while starting the watcherThread in ThreadDeath…
rubo
force-pushed
the
feature/packaging
branch
from
35f0670 to
31eed7c
Compare
rubo
force-pushed
the
feature/packaging
branch
from
31eed7c to
43ff957
Compare
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
5 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.
Configured and updated package info. In
.csprojfiles, replaced tags have been commented out instead of deleted to mitigate future merge conflicts.This branch has been rebased on the latest
upstream/dev, bringing the v0.7.4 changes from Microsoft. Those changes mostly contain build and packaging-related material, so better have them now to avoid potential merge conflicts in the future. Thus, this branch should be force-pushed todev.