From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] tls and iphones and ios9 (sigh)
Date: Thu, 17 Sep 2015 19:27:56 -0700 [thread overview]
Message-ID: <569e5f18ad12a6a6a3a102a5fac1df65@brasstown.quanstro.net> (raw)
In-Reply-To: <6CD77653-C2BC-45EA-B5B9-9443CEB0E68C@corpus-callosum.com>
On Thu Sep 17 12:49:37 PDT 2015, jas@corpus-callosum.com wrote:
>
> > On Sep 17, 2015, at 12:46 PM, Skip Tavakkolian <9nut@9netics.com> wrote:
> >
> >> combover. I see what you did there.
> >
> > ha! i can trump that…
>
> There’s a direct correlation to length of hair and billable rate.
lucky me.
- erik
next prev parent reply other threads:[~2015-09-18 2:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 14:33 Steve Simon
2015-09-17 15:42 ` Jeff Sickel
2015-09-17 16:38 ` erik quanstrom
2015-09-17 17:46 ` Skip Tavakkolian
2015-09-17 19:47 ` Jeff Sickel
2015-09-18 2:27 ` erik quanstrom [this message]
2015-09-18 8:28 ` Brantley Coile
2015-09-18 9:04 ` hiro
2015-09-18 3:19 ` Andrew Simmons
2015-09-18 9:51 ` Steve Simon
2015-09-18 11:10 ` cinap_lenrek
2015-09-18 13:01 ` erik quanstrom
2015-09-18 13:32 ` cinap_lenrek
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=569e5f18ad12a6a6a3a102a5fac1df65@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).