5f59a02e5320b62a68ad704da17e0ff4/comments/ef62c5e84ed7e3571f9d9c8ced81f49d/description

@@ -1,3 +0,0 @@
-What do you mean by ent updating itself?
-
-Do you mean it git clones itself and cargo builds and installs itself?

781360ade670846ed0ccdbfd19ffa8fd/description

@@ -1,15 +0,0 @@
-add a layer to the architecture with a DB api between the FS and ent?
-
-This issue grew out of the discussion in issue
-08f0d7ee7842c439382816d21ec1dea2.
-
-Currently the entomologist crate code directly reads and writes files
-and calls `git commit` when it wants.  The directory is managed by the
-application, generally as an ephemeral worktree containing a (possibly
-detached) checkout of the `entomologist-data` branch.
-
-We may be able to simplify the ent internals (and the application)
-by adding a "database" API between ent and the filesystem.
-
-There is some preliminary design brainstorming in the issue mentioned
-above.

7bf773d64437d6b92b7ffe6932531533/description

@@ -1,9 +0,0 @@
-fix parse error in `ent done-time`
-
-Got this error when i typoed the RFC 3339 time (missing `:` in timezone
-offset):
-    $ ent done-time 8c73c9fd5bc4f551ee5069035ae6e866 2025-07-07T22:29:25-0600
-
-    thread 'main' panicked at src/bin/ent/main.rs:503:26:
-    called `Result::unwrap()` on an `Err` value: ParseError(Invalid)
-    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

8c73c9fd5bc4f551ee5069035ae6e866/done_time

@@ -1 +0,0 @@
-2025-07-07T22:29:25-06:00