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

Re: bug in en/header-split-cache-h-part-3, was Re: What's cooking in git.git (Jun 2023, #05; Tue, 20)

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 21, 2023, 22:03 UTC
Message-ID
<xmqqjzvwfp6f.fsf@gitster.g>
In-Reply-To
<20230621202642.GA1423@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 23 quoted lines
> Yeah. I guess the real build problem is actually in the merge of split-2
> (it conflicted with a simultaneous topic, hence the fix coming in the
> merge). So another option to address that here would be to amend the
> 4bd872e0ed (Merge branch 'en/header-split-cache-h-part-2' into
> en/header-split-cache-h-part-3, 2023-05-08) to include that fixup.
>
> As for the others, I'd consider:
>
>   1. (optional) Drop the #ifndef at the very start of the series, before
>      we touch anything, with the rationale that it is not doing anything
>      and masks errors. I don't _think_ this can ever backfire, because
>      we unconditionally set DEFAULT_GIT_TEMPLATE_DIR (unlike some other
>      things like DEFAULT_PAGER, where the Makefile might leave it
>      unset). But we can also leave this out, or do it as a separate
>      topic, if we want to minimize changes / risk of screwing something
>      up.
>
>   2. Squash the Makefile fix into the "adopt shared init-db" patch
>      (currently 0d652b238).
>
> And that would leave the result fully bisectable. But if we prefer to
> keep the history closer to reality, I can prepare the Makefile thing as
> a patch on top.
I've done the messiest, I guess ;-)
 * revert merge of the part-3 topic and Dscho's cmake fix out of 'next'.
 * rebase part-3 on top of the more recent 'master'.
 * squash in the two hunks (including setup.c change) from you into
   the "setup: adopt shared init-db & clone code" step.
 * squash in Dscho's cmake fix into "cache.h: remove this
   no-longer-used header" step.

The result is not in 'next' yet until I hear something from those who have been involved in the topic, including Elijah and Dscho.

Thanks.
Previous: Jeff KingNext: Elijah Newren
Message 5 of 8 in “What's cooking in git.git (Jun 2023, #05; Tue, 20)”
  1. Junio C HamanoJun 21, 2023
  2. bug in en/header-split-cache-h-part-3, was Re: What's cooking in git.git (Jun 2023, #05; Tue, 20)Jeff King, Jun 21, 2023
  3. Junio C HamanoJun 21, 2023
  4. Jeff KingJun 21, 2023
  5. Junio C HamanoJun 21, 2023
  6. Elijah NewrenJun 23, 2023
  7. Junio C HamanoJun 23, 2023
  8. Jeff KingJun 24, 2023

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.