<p>This week I realised that <a href="https://hachyderm.io/tags/git" class="mention hashtag" rel="tag">#<span>git</span></a> bundles are even more awesome than I thought. And I was a fan of them already!</p><p>git bundles are my favourite way to receive patches by email. They&#39;re very small; a single file can contain a whole series of commits, instead of having to cat-herd one attachment per patch (or worse, one _email_ per patch); they&#39;re so obviously binary that not even a really bad MUA is likely to &quot;helpfully&quot; do text processing on them, and a user isn&#39;t tempted to paste them into the message body instead of making them a proper attachment. Also, they explicitly state which existing commit the changes started from, which is helpful for handling conflicts, and for knowing what you expect the sender to have taken account of.</p><p>But this week I realised there&#39;s one more advantage: if the same commit appears in more than one bundle, it will be reliably recognised as identical. This is helpful when you&#39;re the one _sending_ the bundle.</p><p>Suppose I send someone 3 patches. Half an hour later I smite my forehead and realise I need to send one more. With &#39;git format-patch&#39; I probably send just the extra patch, so that the recipient has to extract attachments from two emails and apply them in the right order. Or I send all 4 patches in email #2, and the recipient gets errors if they do the obvious thing with that email after they&#39;ve already applied the patches from #1.</p><p>But with git bundles, I can send a bundle of all 4 commits in email #2, and it will do the right thing _regardless_ of whether the recipient had already pulled from the previous bundle in email #1!</p>