Local Alleles (PR #434) applied to VCFv4.4 #745
Closed
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
|
Incidentally, diff PDF previews include all pages rather than only the changed pages due to a ghostscript bug that was fixed two months ago but has not yet appeared in a release. So that's fun… |
|
@d-cameron: Please comment (or just do it!) on whether you wish to convert PR #434 to apply to the VCFv4.4 document by force-pushing this PR's HEAD to Yossi's PR's branch. |
|
PR #434 now contains this update. |
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.
This draft PR applies #434's Local Allele changes to the VCFv4.4 document on top of current master. It is not intended to split the conversation from the existing PR, but to provide a preview PDF and demonstration of how this applies to current v4.4.
If the PR author and VCF maintainers agree, and wish to apply the local alleles additions to v4.4 instead of v4.3 (or perhaps to both), then we can force push #434's branch to this commit, close this PR, and continue the conversation on the original PR.