From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2025, #02; Mon, 4)
Date: Thu, 7 Aug 2025 06:43:17 +0200 [thread overview]
Message-ID: <aJQu5VJ_w1Vq_VYW@pks.im> (raw)
In-Reply-To: <xmqqfre4tahh.fsf@gitster.g>
On Wed, Aug 06, 2025 at 02:18:34PM -0700, Junio C Hamano wrote:
> SZEDER Gábor <szeder.dev@gmail.com> writes:
>
> > Before merging please make sure that the topic can be built on its
> > own. Currently all of its commits, including the merge commit the
> > topic is based on, fail to build because:
> >
> > $ git log --oneline -1
> > fc33fe7eff (HEAD) Merge branch 'ps/reflog-migrate-fixes' into ps/remote-rename-fix
> > $ make
> > CC builtin/reflog.o
> > builtin/reflog.c:7:10: fatal error: object-store.h: No such file or directory
> > 7 | #include "object-store.h"
> > | ^~~~~~~~~~~~~~~~
> > compilation terminated.
> > make: *** [Makefile:2817: builtin/reflog.o] Error 1
>
> The joy of having too many moving parts X-<.
>
> Thanks for catching.
I guess what I learned is that I'll refrain from building on top of a
topic that hasn't hit "next" yet from now on. I knew it was a going to
become a bit painful, but I guess it's even more so than I expected.
The merge commit does need to rename the include from "object-store.h"
to "odb.h", which is because the parent topic was built on top of
"maint" where the rename hasn't yet happened.
Thanks!
Patrick
next prev parent reply other threads:[~2025-08-07 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 17:24 What's cooking in git.git (Aug 2025, #02; Mon, 4) Junio C Hamano
2025-08-05 13:55 ` Toon Claes
2025-08-05 18:03 ` Junio C Hamano
2025-08-06 20:47 ` SZEDER Gábor
2025-08-06 21:18 ` Junio C Hamano
2025-08-07 4:43 ` Patrick Steinhardt [this message]
2025-08-07 15:22 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aJQu5VJ_w1Vq_VYW@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder.dev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).