A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.
I upvoted before reviewing the article in situ, then I had to go back and fix my upvote.
A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.
I upvoted before reviewing the article in situ, then I had to go back and fix my upvote.
I was thinking BeOS's BFS since that was the closest I knew off the top of my head, but tmsu looks awesome. I love that simple command line interface around it.
Why stop at a tag-based file manager? Why not a tag-based filesystem?
The first can contain the second but it's not recommended.
Maybe not, but somebody inevitably is. I was never a fan of the arch mods banning necrobumping because if that's the topic thread that comes up in search engine results then it makes sense for the answer to live with the question.
Were you on the discussion on GitHub by chance? https://github.com/orgs/FossifyOrg/discussions/9
What is it you need that a centralized version control system offers that a distributed version control system doesn't? For instance you could use git or pijul for a monorepo.
Heavy overlap with the Rust community I see.
This is what happens when you patent software, folks. You die. Let this be a lesson.
And the site's dark mode is fantastic...
Have you tried Immich? It has a very similar feel to Google Photos but with the advantage of owning your storage.
peer-to-peer, as opposed to?
I use Fennec/Firefox with the ublock plugin. How does that compare with cromite?