From: Eli Zaretskii <eliz@gnu.org>
To: dick.r.chiang@gmail.com
Cc: larsi@gnus.org, 48949@debbugs.gnu.org
Subject: bug#48949: 28.0.50; Thread-Process Liberalization
Date: Fri, 11 Jun 2021 13:59:51 +0300 [thread overview]
Message-ID: <83r1h8acpk.fsf@gnu.org> (raw)
In-Reply-To: <871r98d7e3.fsf@dick> (dick.r.chiang@gmail.com)
> From: dick.r.chiang@gmail.com
> Cc: 48949@debbugs.gnu.org
> Date: Fri, 11 Jun 2021 06:26:28 -0400
>
> Well, this response and that of #bug36609 effectively puts the kibosh on
> my dream of Gnus 2.0 (a working version at github.com/dickmao/gnus I
> run rather delightedly every day). It's a more-than-5000 line change thus
> far, so given the vigorous pushback on what I considered to be
> non-controversial changes in #bug48949 and #bug36609, it never really had a
> chance.
I don't understand: why being able to wait for a process that is
locked to another thread is so important for what you wanted to do?
And if it _is_ important, then why not unlock the process, so that its
output could be processed by any thread?
next prev parent reply other threads:[~2021-06-11 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 20:36 bug#48949: 28.0.50; Thread-Process Liberalization dick.r.chiang
2021-06-11 5:53 ` Eli Zaretskii
2021-06-11 10:26 ` dick.r.chiang
2021-06-11 10:59 ` Eli Zaretskii [this message]
2021-06-12 14:51 ` dick.r.chiang
2021-06-12 14:56 ` Eli Zaretskii
2021-06-12 15:09 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r1h8acpk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48949@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).