Make it configurable to end messages with CR LF for TCPSender #12
Conversation
This file contains hidden or 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
perlei
force-pushed
the
feature/optionalCRLF
branch
2 times, most recently
from
74f2a9b to
c68f4f2
Compare
perlei
force-pushed
the
feature/optionalCRLF
branch
from
c68f4f2 to
0310bd4
Compare
Contributor
|
Thanks @perlei ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
My syslog messages ends with "^M" like this one:
It would be nice to make it optional to include the \r\n , this PR makes that possible
This PR makes it possible to add any kind of postfix to the messages.