From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: js/scalar, was Re: What's cooking in git.git (Oct 2021, #05; Mon, 18)
Date: Fri, 22 Oct 2021 17:55:45 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2110221734530.62@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <211022.868rylkuw7.gmgdl@evledraar.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
Hi Ævar,
On Fri, 22 Oct 2021, Ævar Arnfjörð Bjarmason wrote:
> On Thu, Oct 21 2021, Johannes Schindelin wrote:
>
> > tl;dr it isn't worth your nor my time for you to focus on the build
> > process in contrib/scalar/ at this moment.
I still stand by these words, and I think you completely glanced over this
problem. Your focus seems to lie exclusively on those "dependency
problems". But apart from you, who cares if `libgit.a` is not rebuilt in
obscure and rare circumstances _when building something in `contrib/`_?
The code in `contrib/scalar/` is transitional.
Just forget about Scalar's build process. Forget about getting its CI to
work. I have all that figured out already. It is all working as well as
needed.
> > Having said that, I do appreciate your interest in this patch series, and
> > I have suggestions at the end of this mail how we could collaborate on it
> > in a more fruitful manner.
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.
Ciao,
Dscho
> [... skipping a lot of talk about "fixing" the build problems that I do
> not consider problems at all at this stage, and probably also not later
> because I want Scalar _not_ to be integrated more closely into Git's
> build process as I have pointed out multiple times even while you are
> continuously trying to push for the exact opposite of that and I am
> starting to feel a bit unheard...]
next prev parent reply other threads:[~2021-10-22 15:55 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 [this message]
2021-10-26 12:20 ` Ævar Arnfjörð Bjarmason
2021-10-27 23:56 ` Junio C Hamano
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=nycvar.QRO.7.76.6.2110221734530.62@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).