~robby on Nostr: npub1zglpd…crqd7 npub1dtw0v…885ra How about sending a PR over email, instead of ...
npub1zglpd69ltamxe7nnm6rdfleu8amgg3sn24n8rvdey6avckmeax8qvcrqd7 (npub1zgl…rqd7) npub1dtw0ve3yrtslcda2l46lmm7t5z7m7sc6xf9r7cd98e37pd92utdsd885ra (npub1dtw…85ra) How about sending a PR over email, instead of the patches themselves?
https://git-scm.com/docs/git-request-pull
It seems like this flow would minimize complexity of email based development, while retaining many (but not all) of the benefits for offline work. I have never actually used this flow though, so I'm not sure how well it works in practice.
https://git-scm.com/docs/git-request-pull
It seems like this flow would minimize complexity of email based development, while retaining many (but not all) of the benefits for offline work. I have never actually used this flow though, so I'm not sure how well it works in practice.