Skip to content

Use Logs library for logging - #199

Merged
yomimono merged 1 commit into
mirage:masterfrom
talex5:logs
May 3, 2016
Merged

yomimono merged 1 commit into
mirage:masterfrom
talex5:logs

Conversation

@talex5

@talex5 talex5 commented May 3, 2016

Copy link
Copy Markdown
Contributor

Note: to avoid breaking the API, this patch does not yet remove the (now-unused) console arguments from the signatures. This is so that this patch can be merged quickly to avoid creating more conflicts with other refactoring work going on.

Note: to avoid breaking the API, this patch does not yet remove the
console arguments from the public API.
@talex5 talex5 mentioned this pull request May 3, 2016
@yomimono
yomimono merged commit a54f638 into mirage:master May 3, 2016
@yomimono

yomimono commented May 3, 2016

Copy link
Copy Markdown
Contributor

Looks great to me! Thanks!

@hannesm

hannesm commented May 4, 2016

Copy link
Copy Markdown
Member

this is great! I'm uncertain about choice of log levels (should we come up with some guidelines? is info a reasonable default for all the messages?). and there's still a custom logging framework in tcp https://github.com/mirage/mirage-tcpip/blob/master/tcp/log.ml -- which should now use logs, shouldn't it?

@talex5

talex5 commented May 4, 2016

Copy link
Copy Markdown
Contributor Author

I kept most of them at info to avoid changing the behaviour too much in this PR, but feel free to make additional PRs to discuss adjustments to them.

The pre-existing logging does some stats too, so might need a bit of adjusting to move it over (but would be welcome I think). @samoht knows more about this...

samoht pushed a commit to samoht/mirage-tcpip that referenced this pull request Apr 4, 2017
Use Logs library for logging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants