diff options
author | Bradley Taunt <bt@btxx.org> | 2024-07-02 14:22:21 -0400 |
---|---|---|
committer | Bradley Taunt <bt@btxx.org> | 2024-07-02 14:22:21 -0400 |
commit | 3f6a9546ec13063d0d5bdf21d30a93d3e8aa6050 (patch) | |
tree | 947985c4eda1bceb1910bc01739c32fd0baad181 /build/posts/mail/index.html | |
parent | 14074019d62d98885c4c764401a9e7e1fd129f79 (diff) |
Diffstat (limited to 'build/posts/mail/index.html')
-rw-r--r-- | build/posts/mail/index.html | 61 |
1 files changed, 0 insertions, 61 deletions
diff --git a/build/posts/mail/index.html b/build/posts/mail/index.html deleted file mode 100644 index afc87bc..0000000 --- a/build/posts/mail/index.html +++ /dev/null @@ -1,61 +0,0 @@ -<!doctype html> -<html lang="en"> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - <meta name="color-scheme" content="dark light"> - <link rel="icon" href="data:,"> - <title>Working with `git` Patches in Apple Mail</title> - <link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" /> - <link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" /> -<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> -</head> - -<nav> - <a href="#menu">Menu ↓</a> -</nav> - -<main> -<h1 id="working-with-patches-in-apple-mail">Working with <code>git</code> Patches in Apple Mail</h1> -<p>2023-05-11</p> -<blockquote> -<p><strong>Before we begin</strong>: You could likely automate this process in a more streamlined way, but for most use cases this workflow should be fine.</p> -</blockquote> -<p>I recently covered how to <a href="/git-patches">work with git email patches in Evolution on Linux</a>, so I thought it would make sense to walk through a similar workflow for those using Apple Mail on MacOS. The idea is essentially the same, with just a little extra work involved.</p> -<h2 id="create-a-patches-mailbox">Create a “Patches” Mailbox</h2> -<p>The first thing you’ll need to do is make a new <code>Patches</code> mailbox folder inside your existing mail account. Once done, your default Mail sidebar should look similar to the following:</p> -<p><img src="/public/images/apple-mail-1.png" alt="The Apple Mail sidebar with the Patches folder present" /></p> -<p><em>The Apple Mail sidebar with the “Patches” folder present</em></p> -<h2 id="applying-patches">Applying Patches</h2> -<p>Now navigate to the email message containing a <code>git</code> patch. Right-click and select <em>Move to</em> > <em>Patches</em>. Now in the sidebar, right-click your <em>Patches</em> folder and select <em>Export Mailbox…</em>. You’ll be prompted to save this folder locally. I suggest having a top-level folder named <strong>Patches</strong> to make things consistent.</p> -<p>Inside this folder you should see something similar to the following structure:</p> -<p><img src="/public/images/apple-mail-2.png" alt="The contents of the saved Patches mailbox folder" /></p> -<p><em>The contents of the saved Patches mailbox folder</em></p> -<p>Once saved, open your terminal, navigate to the project you wish to apply this new patch to:</p> -<pre><code>cd my-path/very-cool-project -</code></pre> -<p>and then run:</p> -<pre><code>git apply ~/Patches/<saved-patches-mailbox-folder>/mbox -</code></pre> -<p>Congrats! You’ve successfully applied a git email patch through Apple Mail! Well, kind of. The terminal did most of the <em>real</em> work. Just be sure to periodically <em>purge</em> your local <em>Patches</em> folder to keep things clean!</p> -<footer role="contentinfo"> - <h2>Menu Navigation</h2> - <ul id="menu"> - <li><a href="/">Home</a></li> - <li><a href="/projects">Projects</a></li> - <li><a href="/uses">Uses</a></li> - <li><a href="/wiki">Wiki</a></li> - <li><a href="/resume">Resume</a></li> - <li><a href="/colophon">Colophon</a></li> - <li><a href="/now">Now</a></li> - <li><a href="/donate">Donate</a></li> - <li><a href="/atom.xml">RSS</a></li> - <li><a href="#top">↑ Top of the page</a></li> - </ul> - <small> - Built with <a href="https://git.sr.ht/~bt/barf">barf</a>. <br> - Maintained with ♥ for the web. <br> - Proud supporter of <a href="https://usefathom.com/ref/DKHJVX">Fathom</a> & <a href="https://nextdns.io/?from=74d3p3h8">NextDNS</a>. <br> - The content for this site is <a href="https://creativecommons.org/licenses/by-sa/2.0/">CC-BY-SA</a>.<br> The <a href="https://git.sr.ht/~bt/bt.ht">code for this site</a> is <a href="https://git.sr.ht/~bt/bt.ht/tree/master/item/LICENSE">MIT</a>. - </small> -</footer>
\ No newline at end of file |