From: Silas McCroskey <inkswinc@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] vt(1): document ability to pass a command
Date: Thu, 28 Jan 2021 11:25:41 -0800 [thread overview]
Message-ID: <CAHjwAuxsWEp8XQLHNs5vhiY1zd4WWHwPsFGqercUZO+X9bfc-A@mail.gmail.com> (raw)
In-Reply-To: <F66CE226CAADBE13F49B8E8A98BB1915@musolino.id.au>
Ah, that was like the day after I last updated =)
Good to see.
- sam-d
prev parent reply other threads:[~2021-01-28 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 7:35 Silas McCroskey
2021-01-28 9:29 ` Alex Musolino
2021-01-28 19:25 ` Silas McCroskey [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=CAHjwAuxsWEp8XQLHNs5vhiY1zd4WWHwPsFGqercUZO+X9bfc-A@mail.gmail.com \
--to=inkswinc@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).