🚀 Wow, hold onto your beanies, folks! It's 2025, and we're still pretending that the arcane sorcery of "git #rebase --onto" is accessible to mere mortals. 💀🤣 Remember, the key to mastering #stacked #diffs is to revel in the Sisyphean joy of wrestling with outdated documentation and unhelpful error messages! 🎉
https://dineshpandiyan.com/blog/stacked-diffs-with-rebase-onto/ #git #git #tips #developer #humor #coding #challenges #HackerNews #ngated
Stacked Diffs with `git rebase --onto`

Using git `rebase --onto` workflow to work with stacked diffs

#Code reviews on #Open Build Service just got easier. The new Changes tab keeps #diffs and #comments together, making feedback more focused and organized. Check it out. #openSUSE #OBS https://openbuildservice.org/2025/09/18/explaining-diff-comments/
A Better Way to Discuss Code: Diff Comments

By now, many OBS users have noticed that the Changes tab has its own place, and for good reason.

Open Build Service

Diffsitter – A Tree-sitter based AST difftool to get meaningful semantic diffs

https://github.com/afnanenayet/diffsitter

#HackerNews #Diffsitter #Tree-sitter #AST #Difftool #Semantic #Diffs #GitHub

GitHub - afnanenayet/diffsitter: A tree-sitter based AST difftool to get meaningful semantic diffs

A tree-sitter based AST difftool to get meaningful semantic diffs - afnanenayet/diffsitter

GitHub
Came up at work but definitely a question of general interest:

I feel like when looking at a line-by-line diff of an XML file, it's just...
really not super clear, even with highlighting and such. Is there any sort of graph-aware diff tool that might generate a visual graph and show the difference that way? So that rather than reviewing line by line, you can say "ah, a node has moved from being a child of this node to another", or "these two nodes have been merged into one".

I feel like it would be possible to gin something up in like, networkX or something, but if there's prior art...

#techPosting #XML #computerScienceTrees #graphs #diffs
When you start going through #objdump #diffs it may be time to question your life choices. #headscratcher
kernel/git/torvalds/linux.git - Linux kernel source tree

Here is a tip for anybody learning #Git and is confused by #merging and #rebasing

We all know git stores commits as snapshots. However, when it comes to merging and rebasing, it's better to think of commits as #diffs that introduce changes (the thing you get with git diff). You are actually combining, splitting, rearranging or deleting diffs - not snapshots.

This requires a slight change in your mental model of git. But the operations will make sense immediately.

I cannot imagine living without file revisioning, like #git

Having used them daily for the previous 30 years, I don't understand how developers work without #branches, #merging, #diffs.

#visualsourcesafe #cvs #svn #hg #git it doesn't matter - it's the concept of revisioning and being and to "go back in time".

#Revisioning also for binaries, Word documents and Excels, of course. What else?