New tinylog entry
This commit is contained in:
parent
3906ccf8e4
commit
17f5927697
1 changed files with 8 additions and 4 deletions
|
@ -4,10 +4,10 @@ Meta(
|
||||||
published: Some(Time(
|
published: Some(Time(
|
||||||
year: 2023,
|
year: 2023,
|
||||||
month: 6,
|
month: 6,
|
||||||
day: 10,
|
day: 15,
|
||||||
hour: 13,
|
hour: 4,
|
||||||
minute: 55,
|
minute: 8,
|
||||||
second: 59,
|
second: 28,
|
||||||
)),
|
)),
|
||||||
tags: [
|
tags: [
|
||||||
"tinylog",
|
"tinylog",
|
||||||
|
@ -17,6 +17,10 @@ Meta(
|
||||||
Some shorter thoughts and updates that might not warrant a full gemlog entry. I'll probably be using this to post updates on my various projects in a much more regular fashion.
|
Some shorter thoughts and updates that might not warrant a full gemlog entry. I'll probably be using this to post updates on my various projects in a much more regular fashion.
|
||||||
|
|
||||||
=> .. Home
|
=> .. Home
|
||||||
|
## 2023-06-15 04:08 UTC
|
||||||
|
I decided to install FreeBSD on actual hardware again and had some interesting complications. I had a full gemlog post ready to go about it actually, but one of the complications lead to some data loss, so I'll have to put it all back together again.
|
||||||
|
|
||||||
|
In other news, I've been forgetting to git commit/push/pull when updating this tinylog and had to clean up a bad merge earlier. No posts should have been lost, which is the great thing about putting it all into VC, but obviously my workflow needs updated.
|
||||||
## 2023-06-10 13:55 UTC
|
## 2023-06-10 13:55 UTC
|
||||||
The latest Dory commits center around an iso-8601 time implementation, which is the format that `timestamp` lines are supposed to use in messages. The spec is of course a little ambiguous, and iso8601 allows dates in one of three formats, with the further distinction that there is both a `basic` formatting and an `extended` formatting, where the difference is the appearance of separators between the fields. I've decided for expediency to only implement `calendar` style dates, which is the traditional yyyy-mm--dd format that we're all used to seeing.
|
The latest Dory commits center around an iso-8601 time implementation, which is the format that `timestamp` lines are supposed to use in messages. The spec is of course a little ambiguous, and iso8601 allows dates in one of three formats, with the further distinction that there is both a `basic` formatting and an `extended` formatting, where the difference is the appearance of separators between the fields. I've decided for expediency to only implement `calendar` style dates, which is the traditional yyyy-mm--dd format that we're all used to seeing.
|
||||||
## 2023-06-07 20:36 UTC
|
## 2023-06-07 20:36 UTC
|
||||||
|
|
Loading…
Add table
Reference in a new issue