thunderbird-patch-review
Simple email patch review tool for Thunderbird
git clone git://mccd.space/thunderbird-patch-reviewcommit a9dc4a391a8d7d92eb1f4b63eea9f089e1006510
parent fdfddc9000179c969bfcff367f654e265a0b01d4
Author: Marc <marc@coquand.email>
Date: Sun, 19 Jul 2026 17:09:40 +0200
Update README
Diffstat:
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/README.html b/README.html
@@ -16,13 +16,7 @@
<figcaption>Fig: Patch overview</figcaption>
<img style="max-width: 100%" src="/assets/thunderbird-patch-overview.png"/>
</figure>
-
- <figure>
- <figcaption>Fig: Sourcehut integration.</figcaption>
- <img style="max-width: 100%" src="/assets/srht-integration-thunderbird.png"/>
- </figure>
-
<figure>
<figcaption>Fig: Apply patches from the UI.</figcaption>
<img style="max-width: 100%" src="/assets/thunderbird-patch-success.png"/>
@@ -33,6 +27,10 @@
<img style="max-width: 100%" src="/assets/thunderbird-patch-fail.png"/>
</figure>
+ <figure>
+ <figcaption>Fig: Sourcehut integration.</figcaption>
+ <img style="max-width: 100%" src="/assets/srht-integration-thunderbird.png"/>
+ </figure>
<h2>Installation (source)</h2>
<p>Package the extension source code as an .xpi and install it via
@@ -50,11 +48,11 @@
changed files as arguments. Use a non-blocking GUI-capable command
such as <code>code -n</code> or <code>emacsclient -n</code>; a bare
terminal editor has no terminal to open in. Empty means
- <code>$EDITOR</code>.</p></dd>
+ <code>$EDITOR</code>.</p></dd>
<dt>Apply strategy</dt>
<dd><p><code>git am --3way</code> (default) or plain
- <code>git am</code>.</p></dd>
+ <code>git am</code>.</p></dd>
<dt>Repository mappings</dt>
<dd><p>Substring matches against a patch's List-Id header or
@@ -114,9 +112,8 @@
<h2>Disclaimer</h2>
<p>This add-on was vibe coded using GLM5.2 and built to solve the
needs of my team. I was hesitant to share it, as I generally do not
- like vibe-coded projects and do not want to endorse the use of LLMs.
- However, given that a tool like this is sorely lacking from the
- ecosystem, I decided to share it anyway.</p>
+ like vibe-coded projects. However, given that a tool like this is
+ sorely lacking from the ecosystem, I decided to share it anyway.</p>
<p>I have not reviewed the code line-by-line, but I designed the
general approach the system should use, and focused on using as