From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Ramsay Jones <ramsay@ramsayjones.plus.com>,
Patrick Steinhardt <ps@pks.im>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] Makefile: fix up lib directory move
Date: Sun, 12 Jul 2026 07:02:35 -0700 [thread overview]
Message-ID: <xmqqbjcc5mro.fsf@gitster.g> (raw)
In-Reply-To: <ef422523-1c50-ec79-e89a-f43f02ba1ca7@gmx.de> (Johannes Schindelin's message of "Sun, 12 Jul 2026 12:15:23 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi Ramsay,
>
> On Fri, 10 Jul 2026, Ramsay Jones wrote:
>
>> Commit 9759608622 ("Move libgit.a sources into separate "lib/" directory",
>
> It's not your fault, but this commit is no longer reachable from any
> official branch.
>
> Maybe a more stable way to refer to this right now would be to name the
> topic: `ps/libgit-in-subdir`.
Yes, citing the object name alone would have been useless.
On the other hand, it is good to have it as a sanity-checking
clue. If or when the patch does not apply cleanly, we can tell
that the fix-up was written based on an older iteration. The
"reference" format used here carries more information than the
topic branch name alone, and with the commit title, we can run
$ git show 'origin/seen^{/^Move libgit\.a sources into}'
when 9759608622 cannot be found.
>> 2026-06-22) moved some files into a lib directory, but forgot to update
>> a sparse dependency in the Makefile, resulting in a sparse error:
>>
>> SP lib/pack-revindex.c
>> lib/pack-revindex.c:78:17: error: memset with byte count of 262144
>> make: *** [Makefile:3446: lib/pack-revindex.sp] Error 1
>>
>> Add the missing 'lib/' prefix to the pack-revindex.sp path.
>
> That reasoning and that patch make sense to me. Thank you!
Yes, indeed. It is queued on top of the topic.
Thanks.
next prev parent reply other threads:[~2026-07-12 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 18:38 [PATCH] Makefile: fix up lib directory move Ramsay Jones
2026-07-12 10:15 ` Johannes Schindelin
2026-07-12 13:35 ` Ramsay Jones
2026-07-12 14:02 ` Junio C Hamano [this message]
2026-07-13 5:22 ` Patrick Steinhardt
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=xmqqbjcc5mro.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=ramsay@ramsayjones.plus.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