This repository has been archived by the owner on Apr 1, 2024. It is now read-only.
Add forked repo context to top-level README #58
Merged
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
Closed
mattnibs
approved these changes
Apr 12, 2022
|
Going to merge without build passing since this doesn't effect build and is useful information to have on the readme. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
As Windows Defender no longer seems to pop up panicky messages when Brim is installed, it seems like the Microsoft Windows beta limitations disclaimers can be removed soon. As that doc had also been a place to disclose the details of Brim's port of Zeek, this PR proposes moving that info to the README in the Zeek fork itself. Since this repo is linked to from Brimcap materials, it all seems like a more appropriate place to cover this for interested parties.