-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: temporarily remove boringcrypto references #97
Conversation
This commit removes boringcrypto references until #64 is resolved.
We could use a specific string in all commented text blocks. For example something like this:
Then later, we can grep for that partial string and make a go/no-go call on the hidden content |
@clayton-cornell In this particular case the content definitely will be removed until 1.1, since we won't have boringcrypto back in place until then. |
@rfratto This one stalled out? |
Updating to merge now; instead of the comments I'll just remove the irrelevant information and link to this PR in #64 so it can be reverted once boringcrypto support returns |
This reverts commit c9daa54.
This reverts commit c9daa54.
This reverts commit c9daa54.
* misc: build boringcrypto and cngcrypto images for Linux and Windows * docs: document boringcrypto images * Revert "docs: temporarily remove boringcrypto references (#97)" This reverts commit c9daa54. * Apply suggestions from code review Co-authored-by: Clayton Cornell <[email protected]> * docs: use BoringCrypto/CNGCrypto as proper spelling --------- Co-authored-by: Clayton Cornell <[email protected]>
* misc: build boringcrypto and cngcrypto images for Linux and Windows * docs: document boringcrypto images * Revert "docs: temporarily remove boringcrypto references (grafana#97)" This reverts commit c9daa54. * Apply suggestions from code review Co-authored-by: Clayton Cornell <[email protected]> * docs: use BoringCrypto/CNGCrypto as proper spelling --------- Co-authored-by: Clayton Cornell <[email protected]>
This commit removes boringcrypto references until #64 is resolved.
cc @clayton-cornell I'm not sure if commenting out the old blocks was the best move here, but I'm a little worried we'll forget all the places where it was mentioned if I removed them outright. WDYT? I could just link to this PR from #64 instead of commenting things out.