extras: timestamp for journal entries #123
Open
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
mcr
approved these changes
Sep 1, 2022
Can't currently put options on captured log messages... (Also adding a nanosecond timestamp in the next commit.)
... to allow nanosecond resolution.
eqvinox
force-pushed
the
journal-entry-timestamp
branch
from
dce30c8 to
3c35843
Compare
Contributor
Author
I can't, this one depends on the options block added in #122, as it is adding an option for use inside of that block… The commits shared between #122 and #123 are the exact same commits (same hash), merging #122 will make the first 2 commits disappear from this PR. |
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.
... to allow nanosecond resolution.
Not much to say here, just useful to have a way of encoding nanosecond precision timestamps.