From: William Casarin <jb55@jb55.com>
To: notmuch@notmuchmail.org
Subject: Washing GitHub emails to include inline patch?
Date: Thu, 21 Sep 2017 09:34:57 -0700 [thread overview]
Message-ID: <87d16kf1se.fsf@jb55.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 100 bytes --]
Hey team,
Most of the patches I review these days comes in as GitHub emails that
look like this:
[-- Attachment #2: Type: message/rfc822, Size: 660 bytes --]
https://github.com/monstercat/iris/pull/52
-- Commit Summary --
* Fix merge conflict putting location search into non-clean-ui iris
-- File Changes --
M bin/js/main.js (66)
M bin/js/users.js (71)
M html/head.html (2)
M templates/users.html (68)
-- Patch Links --
https://github.com/monstercat/iris/pull/52.patch
https://github.com/monstercat/iris/pull/52.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/monstercat/iris/pull/52
[-- Attachment #3: Type: text/plain, Size: 278 bytes --]
I wonder if it would be be possible to wash this email by downloading
the patch and present it inline like git-send-email. This would allow me
to review patches without having to click around the GitHub interface.
Has anyone done this?
Cheers,
William
--
https://jb55.com
next reply other threads:[~2017-09-21 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 16:34 William Casarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-22 1:49 Washing GitHub emails to include inline patch? Kyle Meyer
2017-09-22 14:17 ` Tomi Ollila
2017-09-22 14:57 ` Kyle Meyer
2017-09-22 21:38 ` William Casarin
2017-10-10 17:35 ` William Casarin
2017-10-10 19:54 ` Kyle Meyer
2017-10-11 1:45 ` William Casarin
2017-10-11 3:51 ` Kyle Meyer
2017-10-11 4:38 ` William Casarin
2017-10-12 19:28 ` William Casarin
2017-10-13 5:24 ` Kyle Meyer
2017-10-13 6:03 ` William Casarin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d16kf1se.fsf@jb55.com \
--to=jb55@jb55.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).