From: inkswinc@gmail.com
To: benjapurcell@gmail.com, 9front@9front.org
Subject: Re: [9front] nupas auth: incompatibility and error messaging
Date: Wed, 22 Mar 2017 03:16:18 +0000 [thread overview]
Message-ID: <ebddfe667d3ffd7eb3e01367c33b1321@youmu.sam-d.org> (raw)
In-Reply-To: CAAsuYKeuYOnXmRg0AS8WjaSNVk83kSgbmEX5j7jwfrhBS-fdZQ@mail.gmail.com
Yeah, I realized the failure to check the output of smprint shortly
after posting and have been kicking myself since. I do like your way
better, but wasn't feeling that ambitious and figured I'd go for
something braindead (which I still managed to fuck up). Thanks for
taking it up.
- sam-d
next reply other threads:[~2017-03-22 3:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 3:16 inkswinc [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-22 17:10 inkswinc
2017-03-22 17:09 inkswinc
2017-03-22 9:17 cinap_lenrek
2017-03-22 9:15 cinap_lenrek
2017-03-22 0:02 inkswinc
2017-03-22 2:53 ` [9front] " Benjamin Purcell
2017-03-22 2:58 ` Benjamin Purcell
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=ebddfe667d3ffd7eb3e01367c33b1321@youmu.sam-d.org \
--to=inkswinc@gmail.com \
--cc=9front@9front.org \
--cc=benjapurcell@gmail.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).