git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] Make read_in_full() and write_in_full() consistent with xread() and xwrite()

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 30, 2008, 09:23 UTC
Message-ID
<7vlk2v1ysk.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080427182158.GA29232@zakalwe.fi>
Heikki Orsila <heikki.orsila@iki.fi> writes:
Show 5 quoted lines
> Requesting comments on the following patch.
>
> xread() and xwrite() return ssize_t values as their native POSIX
> counterparts. To be consistent, read_in_full() and write_in_full()
> should also return ssize_t values.
I guess this change would not hurt.
Previous: Heikki Orsila
Message 2 of 2 in “[RFC] Make read_in_full() and write_in_full() consistent with xread() and xwrite()”
  1. Heikki OrsilaApr 27, 2008
  2. Junio C HamanoApr 30, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.