Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
devguide: doc from behavior changes need ticket ref
If a commit introduces code that changes Suricata behavior, the related documentation changes should go in a separate commit, but refer to the same ticket number. This reduces the chances of said changes being lost if there are backports while still keeping the backporting process a bit less bulky, for each commit. Related to Task OISF#6568
- Loading branch information