GNU bug report logs - #48949
28.0.50; Thread-Process Liberalization

Previous Next

Full log

Message #14 received at 48949 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: dick.r.chiang <at> gmail.com
Cc: larsi <at> gnus.org, 48949 <at> debbugs.gnu.org
Subject: Re: bug#48949: 28.0.50; Thread-Process Liberalization
Date: Fri, 11 Jun 2021 13:59:51 +0300

> From: dick.r.chiang <at> gmail.com
> Cc: 48949 <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.