Re: [PATCH v3 05/25] sequencer: eventually release memory allocated for the option values

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Oct 12, 2016, 12:06 UTC
Message-ID: <alpine.DEB.2.20.1610121405410.3492@virtualbox>
In-Reply-To: <xmqq4m4ic0gw.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Tue, 11 Oct 2016, Junio C Hamano wrote:

Show 5 quoted lines

> The only reason why the OPT_STRDUP appeared convenient was because
> options[] element happened to use a field in the structure directly.
> The patch under discussion does an equivalent of
> 
>     app.x_field = xstrdup_or_null(opt_x);

Oh, that xstrdup_or_null() function slipped by me. My local patches use it now.

Ciao, Dscho

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