[$] The ongoing quest for atomic buffered writes
There are many applications that need to be able to write multi-block chunks of data to disk with the assurance that the operation will either complete successfully or fail altoget [...]
https://lwn.net/Articles/1060063/ #LWN #Linux #kernel #Git #PostgreSQL #PostgreSQL #XFS #BPF #io_uring
does Codeberg fully support SHA-256 for git? anyone know?
#git "reset"
```
git stash
git stash drop
```
Oh! I forgot to share the results of #Emacs abstinence experimemt. In these two (or three, I lost count) weeks, I
• Moved all text editing (including my #CommonLisp library maintenance and blog writing) to #ed(1)
• Used console #Git for most workflows, and ed(1) for interactive rebase (I’ve grown to like it)
• Only used Emacs for emails and minor Magit
• Changed three terminals (st -> URxvt -> XFCE Terminal)
• Moved many if my workflows to the browser, because that’s the most featureful platform and ecosystem after Emacs
Overall, I’m relatively confident I can live without Emacs. But such life would be slow, unresponsive, and ineffective. So I’m back to Emacs, because I value my time and sanity. As should you.
Great article on #Git and some of the changing being made.
While I'm happy to see the transition from SHA-1 to SHA-256, the user interface improvements cannot be understated. Git truly is "use 10% of the tools to complete 90% of the work", largely because it's so damn complicated.
https://lwn.net/Articles/1057561/
If you ever used older version control systems like SVN, you were probably taught to think in "diffs".
But Git doesn't think like that 📸 It operates like a mini file system:
✅ When you commit, #Git takes a snapshot of what your files at that moment
✅ If a file didn't change, Git creates a pointer to the previous identical file.
#SmartGit visualizes these snapshots so you can seamlessly jump between different moments in your project's history without the mental gymnastics.

#Worktrees sind das coolste #Git-Feature ever!
Next at #WorkshopsForUkraine: "Oops, #Git! How to recover from common mistakes" by Maëlle Salmon @maelle, Research Software Engineer. Thursday, March 19th, 14:00 CET (note non-standard time). Register or sponsor a place for a student by donating to support #Ukraine. You can also donate to get recordings and all of the materials of the previous workshops. Details: https://sites.google.com/view/dariia-mykhailyshyna/main/r-workshops-for-ukraine#h.r3evto8phau7

Looking for a visual 3-column visual #git #mergetool in #vscode ?
I spent this weekend porting @gnome's Meld merge to a #VsCodeExtension with #gemini. Custom diff connection lines, auto-merge and all. It's still a bit of a mess but it works! Will post updates.
https://marketplace.visualstudio.com/items?itemName=pknowles.meld-auto-merge
I am happy to announce that conflict-buttons.el is on MELPA
https://git.andros.dev/andros/conflict-buttons.el
#emacs #git

Thank you, @maelle for your recent blog post that was highlighted on @rweekly Podcast, https://github.com/zerbiniandrea/conventional-commits.nvim. I learned about Conventional Commits and found this, https://github.com/zerbiniandrea/conventional-commits.nvim, for my Neovim setup!
#Git #ConventionalCommits #nvim
weee let's see how many conflicts this makes