From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: js/scalar, was Re: What's cooking in git.git (Nov 2021, #03; Tue, 9)
Date: Fri, 12 Nov 2021 10:32:35 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2111120854060.21127@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqczn6mtw0.fsf@gitster.g>
Hi Junio,
On Thu, 11 Nov 2021, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > P.S.: The second reason is that I was uncertain as to your decision
> > regarding Stolee's thread about the optimal final location for Scalar.
> > Since it seems that we can actually go forward with `contrib/scalar/`
> > even if you eventually decide you prefer another place, I plan on
> > submitting a new iteration with adjustments for v2.34.0, after that
> > release.
>
> When "make install" at the top-level of the tree starts installing
> "scalar", I'd prefer to see it outside contrib/. That is the only
> preference I can think of right now. Before that happens, if there is a
> way to install it, e.g. "cd contrib/scalar && make install", as long as
> it is clear that it is not yet official, I have no problems with.
Okay, I will rework the patch series so that you can call `make -C
contrib/scalar install`. It is a bit premature, but might help users try
it out.
> There is no hard rule that "git" has to be the only top-level
> command the end-user interacts with. We already ship "gitk" and
> "git-gui" with us, and adding "scalar" to the mix is OK. Some
> people may love it, and others may hate its design choices with
> passion, but that is the same for "gitk" and "git-gui" already.
True.
Thanks,
Dscho
next prev parent reply other threads:[~2021-11-12 9:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 0:59 What's cooking in git.git (Nov 2021, #03; Tue, 9) Junio C Hamano
2021-11-10 12:47 ` js/scalar, was " Johannes Schindelin
2021-11-10 13:42 ` Ævar Arnfjörð Bjarmason
2021-11-11 18:25 ` Junio C Hamano
2021-11-12 9:32 ` Johannes Schindelin [this message]
2021-11-10 13:04 ` jc/fix-pull-ff-only-when-already-up-to-date, " Johannes Schindelin
2021-11-10 17:20 ` Junio C Hamano
2021-11-10 19:00 ` Alex Henrie
2021-11-10 19:09 ` Johannes Schindelin
2021-11-10 19:17 ` Junio C Hamano
2021-11-11 22:19 ` Emily Shaffer
2021-11-11 22:40 ` Emily Shaffer
2021-11-11 22:58 ` Junio C Hamano
2021-11-11 23:44 ` Glen Choo
2021-11-13 9:17 ` ab/config-based-hooks-2 etc. (was: What's cooking in git.git (Nov 2021, #03; Tue, 9)) Ævar Arnfjörð Bjarmason
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.2111120854060.21127@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--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).