From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] rio consctl behaviour
Date: Tue, 2 Jun 2020 21:57:57 +0000 [thread overview]
Message-ID: <CAFSF3XNcg1r8ZafDCr2pN=XtBzHp=Y0ef10w_iUH_YUppPpGiw@mail.gmail.com> (raw)
In-Reply-To: <20F5748B4EDE46E9F35F563470E9D821@prosimetrum.com>
i agree that for hold this doesn't make sense, but no idea if it's
worth changing in case somebody's scripts break...
On 6/2/20, umbraticus@prosimetrum.com <umbraticus@prosimetrum.com> wrote:
> Thanks, eekee. That makes sense re raw mode at least.
> Any problem removing the hold stuff, then, given that,
> as you say, you can easily tell if you're in hold mode?
>
> umbraticus
>
next prev parent reply other threads:[~2020-06-02 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 20:25 umbraticus
2020-06-02 20:49 ` [9front] " Ethan Gardener
2020-06-02 21:53 ` umbraticus
2020-06-02 21:57 ` hiro [this message]
2020-06-02 22:50 ` Silas McCroskey
2020-06-03 2:01 ` umbraticus
2020-06-03 7:37 ` hiro
2020-06-03 20:00 ` Silas McCroskey
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='CAFSF3XNcg1r8ZafDCr2pN=XtBzHp=Y0ef10w_iUH_YUppPpGiw@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).