Re: [PATCH v2 1/4] fetch: extract writing to FETCH_HEAD

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 11, 2021, 19:24 UTC
Message-ID: <xmqqa6tf8eg6.fsf@gitster.c.googlers.com>
In-Reply-To: <X/wnxSn4KjQF0/T+@ncase>

Patrick Steinhardt <ps@pks.im> writes:

Show 10 quoted lines

>> As an abstraction, it may be better to make the caller pass a
>> boolean "is this for merge?" and keep the knowledge of what exact
>> string is used for merge_status_marker to this function, instead of
>> letting the caller passing it as a parameter in the string form.
>> After all, we never allow anything other than an empty string or a
>> fixed "not-for-merge" string in that place in the file format.
>> [Nit #2]
>
> I think it's even nicer to just pass in `rm->fetch_head_status`
> directly, which allows us to move below switch into `append_fetch_head`.

OK.  That may even be better.

Thanks.

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