mirror of
https://github.com/VectorCamp/vectorscan.git
synced 2025-06-28 16:41:01 +03:00
Update README.md
Softened some of the wording around the reason for the fork. ;-)
This commit is contained in:
parent
5298333c73
commit
76bd21e521
11
README.md
11
README.md
@ -12,12 +12,11 @@ all architecture specific -currently Intel- #ifdefs will be removed and abstract
|
|||||||
|
|
||||||
# Why the fork?
|
# Why the fork?
|
||||||
|
|
||||||
Originally, the ARM porting was supposed to be merged into Intel's own Hyperscan, and 2 Pull
|
Originally, the ARM porting was supposed to be merged into Intel's own Hyperscan, and 2
|
||||||
Requests had been made to the project for this reason ([1], [2]). Instead of a review on technical
|
Pull Requests had been made to the project for this reason ([1], [2]). Unfortunately, the
|
||||||
issues, Intel outright rejected any multi-architecture support for Hyperscan, for now and the
|
PRs were rejected for now and the forseeable future, thus we have created Vectorscan for
|
||||||
forseeable future and we were forced to fork. However, we are firm open source believers and
|
our own multi-architectural and opensource collaborative needs.
|
||||||
in the end this can only be a good thing, as it gives us the opportunity to make further
|
|
||||||
modifications and optimizations in the code, which could not be done otherwise.
|
|
||||||
|
|
||||||
# What is Hyperscan?
|
# What is Hyperscan?
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user