Re: [RFC/PATCH 03/18] usage: implement error_errno() the same way as die_errno()

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 26, 2010, 18:35 UTC
Message-ID: <7v8w0gq6fn.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20101125212050.5188.56613.chriscool@tuxfamily.org>

Christian Couder <chriscool@tuxfamily.org> writes:

Show 5 quoted lines

> die_errno() is very useful, but sometimes we don't want to
> die after printing an error message and the error message
> from errno. So let's implement error_errno() that does the
> same thing as die_errno() except that it calls
> error_routine() instead of die_routine().

If this were "error_errno() is to error() as die_errno() is to die(); iow, error_errno() does the same thing as error() but in addition shows the errno information", it might be a good thing, but the above makes it sound like you did something different.

$ 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.