Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14997 > unrolled thread
| Started by | Bize Ma <binaryzebra@gmail.com> |
|---|---|
| First post | 2018-12-29 01:15 -0400 |
| Last post | 2018-12-29 01:15 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: write() not retried after EINTR in printf and echo Bize Ma <binaryzebra@gmail.com> - 2018-12-29 01:15 -0400
| From | Bize Ma <binaryzebra@gmail.com> |
|---|---|
| Date | 2018-12-29 01:15 -0400 |
| Subject | Re: write() not retried after EINTR in printf and echo |
| Message-ID | <mailman.6493.1546060748.1284.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web