From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] cpu/auth
Date: Tue, 28 Jul 2020 11:58:32 +0200 [thread overview]
Message-ID: <CAFSF3XMT8tx5EsDEFxUnAkVk-8dODTuD9RGwOP_FWSeWPkLZ7A@mail.gmail.com> (raw)
In-Reply-To: <20200728052529.GD61790@wopr>
> duplicate was an imperative verb, not an adjective
no
prev parent reply other threads:[~2020-07-28 9:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 1:12 cpu/auth thinktankworkspaces
2020-07-27 12:10 ` [9front] cpu/auth theinicke
2020-07-27 17:12 ` William Gunnells
2020-07-28 3:02 ` William Gunnells
2020-07-28 3:15 ` William Gunnells
2020-07-28 3:51 ` Xiao-Yong Jin
2020-07-28 5:03 ` William Gunnells
2020-07-28 5:21 ` William Gunnells
2020-07-28 5:25 ` Kurt H Maier
2020-07-28 5:47 ` William Gunnells
2020-07-28 5:52 ` William Gunnells
2020-07-28 6:11 ` Stanley Lieber
2020-07-28 6:35 ` thinktankworkspaces
2020-07-28 9:37 ` Ethan Gardener
2020-07-28 9:58 ` hiro [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=CAFSF3XMT8tx5EsDEFxUnAkVk-8dODTuD9RGwOP_FWSeWPkLZ7A@mail.gmail.com \
--to=23hiro@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).