From: ori@eigenstate.org
To: ori@eigenstate.org, driusan@gmail.com, 9front@9front.org
Subject: Re: [9front] What happened to ssh2?
Date: Thu, 15 Aug 2019 00:51:35 -0700 [thread overview]
Message-ID: <01ED80F17658787DCEE735EDDCDE0EF1@eigenstate.org> (raw)
In-Reply-To: 09D026922045BFB6027DDF6743EED58D@eigenstate.org
...And somehow I managed to not realize I was responding to an ancient
email. Please disregard my stupidity.
next reply other threads:[~2019-08-15 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 7:51 ori [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-15 7:48 ori
2017-03-28 14:22 Dave MacFarlane
2017-03-28 15:11 ` [9front] " Stanley Lieber
2017-03-28 19:03 ` Aram Hăvărneanu
2017-03-28 19:05 ` Kurt H Maier
2017-03-28 19:09 ` Aram Hăvărneanu
2017-03-28 19:18 ` Stanley Lieber
2017-03-28 19:34 ` Steve Simon
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=01ED80F17658787DCEE735EDDCDE0EF1@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=driusan@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).