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.
xoggy
joined 1 year ago
When you go to merge master into your feature branch but accidentally squash master in.
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?
But spoons are just tiny bowls to get food from the bigger bowl, man!
The first can contain the second but it's not recommended.
The post is in the positives so I think you're ok. If I had to guess on the downvotes though it's not really a groundbreaking discovery that uni-corn can be broken into two words like that.
The butterfly from The Last Unicorn told us this.
- portable development environment with tmux + neovim + whatever toolchain I'm working in
- various projects I'm developing such as bots or web tools that need uptime or I just don't want to tie down to my local machine
- BOINC
- immich
- minidlna
- nginx reverse proxy with various personal websites behind it
- rsync backup jobs on systemd timers
- rtorrent
- veilid node
Meanwhile 🙄
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.
I don't mean to Dicio but that was a bad pun.