Compare commits
No commits in common. "07bdf39c23304503c11c9615b224978a80e0620c" and "b12e3cc248d550d667eb2c14d5f19d39b6ed2010" have entirely different histories.
07bdf39c23
...
b12e3cc248
4 changed files with 0 additions and 28 deletions
|
|
@ -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?
|
||||
|
|
@ -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.
|
||||
|
|
@ -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
|
||||
|
|
@ -1 +0,0 @@
|
|||
2025-07-07T22:29:25-06:00
|
||||
Loading…
Add table
Add a link
Reference in a new issue