Yes! Infact, the 'change-id' primative is already there with 'patch revision'. We just need clients that will present the changes rather than the whole revision for a better UX. Here is how gitworkshop currently handles it. https://gitworkshop.dev/dan@gitworkshop.dev/ca118aa/prs/note1cv9vzj8zq05g263thrfraqsstauzjsppke8hdvdxy4q7h5he59aqva9tvt This is one thing thing the email-patch workflow does well. Culturally, everyone is expected to integrate changes into their patches rather than layer additional patches on top that apply the fixes.
https://blog.tangled.sh/stacking nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr nostr:npub1useke4f9maul5nf67dj0m9sq6jcsmnjzzk4ycvldwl4qss35fvgqjdk5ks this is interesting.
Could this work more-or-less automatically under NIP-34 by just making patches refer to previous patches with tags? Without using any martial arts?
Discussion
No replies yet.