Skip to content
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

BUGFIX: Update tagFormats to match defined severities #273

Merged
merged 1 commit into from Apr 20, 2016

Conversation

langeland
Copy link
Contributor

Uses the severities descriped in \TYPO3\Flow\Log\LoggerInterface

Uses the severities descriped in \TYPO3\Flow\Log\LoggerInterface
@kdambekalns kdambekalns changed the title [TASK] Update tagFormats to match defined severities TASK: Update tagFormats to match defined severities Feb 25, 2016
@kdambekalns
Copy link
Member

I'd like to see info included to make it B/C and then would be fine with adding to 3.0 even…

@kitsunet
Copy link
Member

Info is included?

@kdambekalns
Copy link
Member

Sorry, I meant success

@langeland
Copy link
Contributor Author

Hmm.. As such I have no problem with adding success, but from what I can see there's no such thing as success in the rfc3164. See page 8 Table 2.

And if I look at: \TYPO3\Flow\Log\Backend\ConsoleBackend::open then success can never be called.

@kdambekalns
Copy link
Member

That's what you get from purely reading a change: I just saw something that was there, was now gone. If it can never end up there, that obviously doesn't matter at all.

👍 after reading the related code as well. Still, that looks like a bugfix and should even go into 2.3…

@kdambekalns kdambekalns changed the title TASK: Update tagFormats to match defined severities BUGFIX: Update tagFormats to match defined severities Feb 25, 2016
@kitsunet
Copy link
Member

looks good 👍

@kitsunet kitsunet merged commit 435cae9 into neos:master Apr 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants