From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: Blame
Date: Thu, 20 Apr 2017 02:59:05 +0200 [thread overview]
Message-ID: <CAHmME9oXUSD7MXu4K_tfcUwBbjPJeh9TjRLHB2z7+-jGJT2v4w@mail.gmail.com> (raw)
In-Reply-To: <CAPX7N=7f_bsENH84RB4=Q6aM48Ng5REZPbTBXnjzNvXY0n7V0w@mail.gmail.com>
Hey Jeff,
If option 1 can be done cleanly enough, that'd be fine with me.
Jason
prev parent reply other threads:[~2017-04-20 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 0:55 Blame whydoubt
2017-04-20 0:59 ` Jason [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHmME9oXUSD7MXu4K_tfcUwBbjPJeh9TjRLHB2z7+-jGJT2v4w@mail.gmail.com \
--to=cgit@lists.zx2c4.com \
/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.
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 NNTP newsgroup(s).