From: Backwoods BC <completely.and.totally.trash@gmail.com>
To: Ken Brown <kbrown@cornell.edu>
Cc: cygwin@cygwin.com
Subject: Re: Another pipe-related problem?
Date: Tue, 9 Nov 2021 19:51:45 -0800 [thread overview]
Message-ID: <CAKwdsS_cYS=31BEfdbDPux+_+gqJra2KTyPm-29Cd9iFy-N9Mw@mail.gmail.com> (raw)
In-Reply-To: <bb6c5229-ce46-5fb3-c8c3-a19c0826d8d5@cornell.edu>
Please pardon the interjection. I'm a hardware guy and any time a
hardware process is in a state where it is waiting for a signal from
another process, I put in a timeout mechanism. Shouldn't this be a
normal practice for software as well?
next prev parent reply other threads:[~2021-11-10 3:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 13:12 Henry S. Thompson
2021-11-08 14:35 ` Ken Brown
2021-11-08 18:52 ` Ken Brown
2021-11-09 10:55 ` Henry S. Thompson
2021-11-09 14:11 ` Ken Brown
2021-11-09 14:47 ` Henry S. Thompson
2021-11-09 22:16 ` Ken Brown
2021-11-09 22:20 ` Ken Brown
2021-11-10 2:53 ` Ken Brown
2021-11-10 3:51 ` Backwoods BC [this message]
2021-11-10 14:47 ` Ken Brown
2021-11-10 17:23 ` Henry S. Thompson
2021-11-10 18:03 ` Ken Brown
2021-11-10 18:42 ` Henry S. Thompson
2021-11-10 23:07 ` Andrey Repin
2021-11-11 11:06 ` Andrey Repin
2021-11-11 14:16 ` Ken Brown
2021-12-08 21:09 ` XEmacs versus Cygwin 3.3 (was Re: Another pipe-related problem?) Henry S. Thompson
2021-12-09 8:39 ` Aidan Kehoe
2021-11-09 23:22 ` Another pipe-related problem? Takashi Yano
2021-11-09 23:29 ` Takashi Yano
2021-11-09 23:48 ` Takashi Yano
2021-11-10 0:16 ` Takashi Yano
2021-11-10 0:37 ` Takashi Yano
2021-11-10 2:02 ` Ken Brown
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='CAKwdsS_cYS=31BEfdbDPux+_+gqJra2KTyPm-29Cd9iFy-N9Mw@mail.gmail.com' \
--to=completely.and.totally.trash@gmail.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).