From: ori@eigenstate.org
To: rgl@antares-labs.eu, 9front@9front.org
Subject: Re: [9front] thread(2): fix manpage typos
Date: Tue, 12 Nov 2019 13:01:29 -0800 [thread overview]
Message-ID: <34281ACA2F3161E57FD479F8E0FA6BB5@eigenstate.org> (raw)
In-Reply-To: 3862DCD22F5F137E8809EED2DA104DEF@antares-labs.eu
> hi.
>
> i'm actually not that sure about the last one, but i still think it's clearer to refer to the procedure instead of a state.
Yes, especially since you can't call 'closed'. Both look good to me, committed.
reply other threads:[~2019-11-12 21:01 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=34281ACA2F3161E57FD479F8E0FA6BB5@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=rgl@antares-labs.eu \
/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).