From: Michael Forney <mforney@mforney.org>
To: 9front@9front.org
Subject: [9front] Re: rc interrupt regression
Date: Fri, 18 Mar 2022 16:33:55 -0700 [thread overview]
Message-ID: <CAGw6cBuYui2QrMkwLUw0Pjrx0_VWAf2H7KD-YXdD8og9M=e18g@mail.gmail.com> (raw)
In-Reply-To: <2Z2GAIQLXW88G.24294JTWIM6TD@mforney.org>
On 2022-03-07, Michael Forney <mforney@mforney.org> wrote:
> Adding back this line fixes the issue for me. Was this a deliberate
> change needed for the unix port? If so, is there some other way to
> solve this problem?
Ping. Any thoughts on this? Has anyone else noticed it?
I've reverted that hunk in my local tree since it kept tripping me up
(did my cp command succeed, or did rc eat it?).
next prev parent reply other threads:[~2022-03-18 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 21:19 [9front] " Michael Forney
2022-03-18 23:33 ` Michael Forney [this message]
2022-03-21 18:08 ` [9front] " cinap_lenrek
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='CAGw6cBuYui2QrMkwLUw0Pjrx0_VWAf2H7KD-YXdD8og9M=e18g@mail.gmail.com' \
--to=mforney@mforney.org \
--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).