From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: js/scalar, was Re: What's cooking in git.git (Oct 2021, #05; Mon, 18)
Date: Wed, 27 Oct 2021 16:56:08 -0700 [thread overview]
Message-ID: <xmqqr1c6t42v.fsf@gitster.g> (raw)
In-Reply-To: <211026.86lf2gym9u.gmgdl@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Tue, 26 Oct 2021 14:20:55 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> It's not that libgit.a isn't rebuilt, that part isn't broken, it's built
> by the top-level Makefile. It's that if you:
>
> make -C contrib/scalar
>
> And then change anything it depends on, short of the top-level
> rebuilding libgit.a it won't be re-built, so for anyone hacking on it
> that Makefile is rather useless.
Is this merely an example, or is this the only thing you cared about
the build procedure?
>> I would still like to invite you to think along more productive lines.
>> It's not about where Scalar's build mechanics are right now. It's where we
>> can take _Git_ to do what Scalar already does.
>
> That's also interesting, but right now we're not discussing that
> subsequent set of patches, but your integration of scalar in-tree. Let's
> fix those issues first.
next prev parent reply other threads:[~2021-10-27 23:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 6:48 What's cooking in git.git (Oct 2021, #05; Mon, 18) Junio C Hamano
2021-10-19 12:45 ` js/scalar, was " Johannes Schindelin
2021-10-20 13:42 ` Ævar Arnfjörð Bjarmason
2021-10-21 8:33 ` Johannes Schindelin
2021-10-22 13:43 ` Ævar Arnfjörð Bjarmason
2021-10-22 15:55 ` Johannes Schindelin
2021-10-26 12:20 ` Ævar Arnfjörð Bjarmason
2021-10-27 23:56 ` Junio C Hamano [this message]
2021-10-19 19:33 ` Johannes Sixt
2021-10-19 22:49 ` Glen Choo
2021-10-20 11:37 ` ab/config-based-hooks-2 Ævar Arnfjörð Bjarmason
2021-10-21 11:32 ` ab/only-single-progress-at-once (was: What's cooking in git.git (Oct 2021, #05; Mon, 18)) Ævar Arnfjörð Bjarmason
2021-10-27 19:26 ` What's cooking in git.git (Oct 2021, #05; Mon, 18) Emily Shaffer
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=xmqqr1c6t42v.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/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).