Git.
It fucking sucks.
@nixCraft Mozilla Firefox
Edit: And yes, I use it ☹️
@melroy @distrowatch @nixCraft svn never fucked itself so badly I had to delete my local copy, download a fresh one, and manually make my changes again. Git does this several times a year.
@falken @melroy @distrowatch @nixCraft
I'm so happy to hear I'm not the only one.
I remember when I was learning git everybody said it was super flexible and you could recover from any mistake you made. This may be true but what they don't tell you is that usually it's a lot easier to start from 0 again.
@pinguino @falken @distrowatch @nixCraft I'm curious what you did that require you to fully need to delete and do a new git clone.
Maybe skill issue 😏?
@melroy @falken @distrowatch @nixCraft
Forgot to gpg sign a commit. Tried some of the solutions I found on the web but none worked and they totally messed my branch.
At the end I just deleted everything, started again from zero and just pasted my new code.
@pinguino @falken @distrowatch @nixCraft if you just want to sign the most recent commit:
git commit -S --amend
@silmathoron @justine @nixCraft cvs and svn are entirely different models for source control.
By "writing changes by hand and printing copies" I mean exactly that, literally. Typing every code (instead of patches) and then printing hard copies of the code for archival.
bash, JavaScript/Node, and PHP, all for the same reason: they're horrible and warty, but ubiquitous
@nixCraft either neovim or docker
1. why would anyone use a worse copy with super hard configuration and dialect if the original is still alive and kicking?
2. why would anyone bother with a way harder to configure and worse container framework if openvz and lxc are still around and kicking?
do you guys like pain?
@nixCraft golang and many of the things related to docker or kubernetes...
But not because of the projects themself and more off because of it getting thrown at problems where it absolutely doesn't make sense...