public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Chet Ramey <chet.ramey@case.edu>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: chet.ramey@case.edu, Andreas Schwab <schwab@linux-m68k.org>,
	       palves@redhat.com, gdb-patches@sourceware.org,
	binutils@sourceware.org,        bug-readline@gnu.org,
	amodra@gmail.com
Subject: Re: [Bug-readline] [PATCH] readline/histfile.c: Check and retry write() operation in history_truncate_file()
Date: Mon, 23 Jun 2014 13:57:00 -0000	[thread overview]
Message-ID: <53A8322D.3010703@case.edu> (raw)
In-Reply-To: <53A638EF.6050700@gmail.com>

On 6/21/14, 10:01 PM, Chen Gang wrote:

>> history_truncate_file will never return -1.
>>
> 
> Hmm... do you mean:
> 
>   "for regular file, write() never return 0, if parameter 'count' > 0?"
> 
>   or
> 
>   "if write() return 0, can also return 0 to history_truncate_file()?".

Both of those things are true, but neither is what I said above.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/

  reply	other threads:[~2014-06-23 13:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  2:36 Chen Gang
2014-06-18 20:33 ` [Bug-readline] " Chet Ramey
2014-06-19  1:31   ` Chen Gang
2014-06-20  8:58     ` Chen Gang
2014-06-20 21:53       ` Chet Ramey
2014-06-21  2:25         ` Chen Gang
2014-06-21 23:19           ` Chet Ramey
2014-06-22  2:01             ` Chen Gang
2014-06-23 13:57               ` Chet Ramey [this message]
2014-06-23 14:59                 ` Chen Gang
2014-06-25 22:16                   ` Chen Gang

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=53A8322D.3010703@case.edu \
    --to=chet.ramey@case.edu \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=bug-readline@gnu.org \
    --cc=gang.chen.5i5j@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=schwab@linux-m68k.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.
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).