#diffs — Public Fediverse posts

Patch applies fake diffs from commit messages

https://samizdat.dev/phantom-patch/

#HackerNews #patching #diffs #commitmessages #softwaredevelopment #cybersecurity

Patch applies fake diffs from commit messages

https://samizdat.dev/phantom-patch/

#HackerNews #patching #diffs #commitmessages #softwaredevelopment #cybersecurity

Patch applies fake diffs from commit messages

https://samizdat.dev/phantom-patch/

#HackerNews #patching #diffs #commitmessages #softwaredevelopment #cybersecurity

Patch applies fake diffs from commit messages

https://samizdat.dev/phantom-patch/

#HackerNews #patching #diffs #commitmessages #softwaredevelopment #cybersecurity

Patch applies fake diffs from commit messages

https://samizdat.dev/phantom-patch/

#HackerNews #patching #diffs #commitmessages #softwaredevelopment #cybersecurity

🚀 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

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

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.

Continuing with #projects, let me talk for a minute about #diffx!

Did you know there's no standard file format for #diffs? No, seriously. I mean, there are Unified Diffs, but that just covers the actual line changes. There's nothing for metadata, no consistency for filename encodings, nothing. It's a mess.

So we're working to solve that with DiffX:

https://diffx.org/

This provides #metadata, parsing rules, mutability, binary files.

All backwards-compatible with common diff variants.