Re: write() not retried after EINTR in printf and echo

From	Bize Ma <binaryzebra@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: write() not retried after EINTR in printf and echo
Date	2018-12-29 01:15 -0400
Message-ID	<mailman.6493.1546060748.1284.bug-bash@gnu.org> (permalink)
References	(1 earlier) <eefa8e88-104a-1fd3-b505-a279778ba291@case.edu> <CAFra36izjDTTFBsRfzsgCr8YGk+n=7O=FiMVX=ivuh5Ejw5MAQ@mail.gmail.com> <996dc3ea-0718-481b-3dc7-4fd358a3a64e@case.edu> <CAFra36gB3JM3R+RWF8JGOE7PEX2D0nvoCKJqWJBxypa0TGHiRg@mail.gmail.com> <CAOSMAutzZS3jCJYmLsQbWrxk4kON78kqF1Ah88P_de5Ct6_+4Q@mail.gmail.com>

Show all headers | View raw

Eduardo Bustamante (<dualbus@gmail.com>) wrote:

>
> (...)

> What if instead of
> complaining you do something about it, like, fixing the problem (send
> a patch)?
>

You are assuming that if I take a look at the c code I will be able to read
it,
then understand it, and then make meaningful, or even reasonable changes
to it. My experience tells me I can not.

Not even read C correctly.

So, sadly I can not send a patch, even if I were to try …

Chet doesn't owe you anything.
>

Of course he doesn't owe me anything.
As much as I don't owe *you* anything.

But as I am reading your complaint to me and I am giving you an answer,
I expect that Chet could be able to read a complaint, take the good parts,
if any, and answer accordingly.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: write() not retried after EINTR in printf and echo Bize Ma <binaryzebra@gmail.com> - 2018-12-29 01:15 -0400

csiph-web