<oembed><type>rich</type><version>1.0</version><author_name>npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_name><author_url>https://nostr.ae/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-05-21&#xA;📝 Original message:On Wed, May 21, 2014 at 1:30 PM, Mark Friedenbach &lt;mark at monetize.io&gt; wrote:&#xA;&gt; Honest question: what would signed commits do to help us here anyway?&#xA;&gt; What&#39;s the problem being solved?&#xA;&gt;&#xA;&gt; Unfortunately git places signatures in the history itself, so it&#39;s not&#xA;&gt; like we could use easily use signatures to indicate acceptance after&#xA;&gt; code review, like we could if we were using monotone for example. Git&#xA;&gt; just wasn&#39;t designed for a commit-signing workflow.&#xA;&#xA;Just makes it easier to sort out things like your git account (or the&#xA;git site) being compromised and used to submit commits.</html></oembed>