From: Mav Straw <maevele@gmail.com>
To: 9front@9front.org
Subject: [9front] about mycroft
Date: Sun, 31 Jul 2022 03:00:43 -0500 [thread overview]
Message-ID: <CALYrE0OWaYnpBkW5qKiecLsJ36g=Cv-iJXrrgriUXOyu+7L1NQ@mail.gmail.com> (raw)
I can't figure out how to respond to posts I've seen in the archive,
but wanted to give some opportunity for any questions I could answer
for you guys. I'm Mav, (otherwise maevele, deadnamed by another name
in the games,) and I'd been mycroft's creative and life partner since
2013 until this past winter. I know some of his closest friends are
among this group, and I understand that no matter my situation with
him, y'all lost somebody important to your community.
I noticed in the other thread, someone wondering whether the last game
was released with my consent, given that the partnership had
dissolved, and yes. We had a discussion about releasing it, and about
including that intro. I was mostly consulting, not writing on that
project, so pretty much all the words are his. I know it's not the big
work he hoped to get done in his lifetime, but its still a good final
work.
Anyway, I'm basically just here to clarify anything you guys are
wondering about regarding mycroft.
Be well,
Mav
reply other threads:[~2022-07-31 8:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CALYrE0OWaYnpBkW5qKiecLsJ36g=Cv-iJXrrgriUXOyu+7L1NQ@mail.gmail.com' \
--to=maevele@gmail.com \
--cc=9front@9front.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.
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).