From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: js/scalar, was Re: What's cooking in git.git (Sep 2021, #02; Wed, 8)
Date: Thu, 9 Sep 2021 13:03:08 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2109091259310.59@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqsfyf5b74.fsf@gitster.g>
Hi Junio,
On Wed, 8 Sep 2021, Junio C Hamano wrote:
> * js/scalar (2021-09-03) 15 commits
> - scalar: accept -C and -c options before the subcommand
> - scalar: implement the `version` command
> - scalar: implement the `delete` command
> - scalar: teach 'reconfigure' to optionally handle all registered enlistments
> - scalar: allow reconfiguring an existing enlistment
> - scalar: implement the `run` command
> - scalar: teach 'clone' to support the --single-branch option
> - scalar: implement the `clone` subcommand
> - scalar: implement 'scalar list'
> - scalar: let 'unregister' handle a deleted enlistment directory gracefully
> - scalar: 'unregister' stops background maintenance
> - scalar: 'register' sets recommended config and starts maintenance
> - scalar: create test infrastructure
> - scalar: start documenting the command
> - scalar: create a rudimentary executable
>
> Add pieces from "scalar" to contrib/.
Thank you for picking it up. It seems as if the reviews are starting to
decrease to a point where I could imagine that we can start talking about
how to refactor things to start bringing the benefits to Git proper.
For what it's worth, I maintain a branch thicket on top of this branch
that has the remaining Scalar parts, both those parts that I still intend
to upstream as well as those parts that will most likely stay in
microsoft/git (e.g. the GVFS protocol-related parts, as it was decided
long ago that the VFS bits won't make it into Git proper, and
microsoft/git only needs these bits for compatibility with Azure Repos).
Here is the CI/PR run of that branch:
https://github.com/dscho/git/actions/runs/1216858695
And much more interesting is the run of the full Scalar Functional Tests
suite: https://github.com/dscho/git/actions/runs/1216858693
(Both pass, of course.)
Ciao,
Dscho
next prev parent reply other threads:[~2021-09-09 11:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 15:38 What's cooking in git.git (Sep 2021, #02; Wed, 8) Junio C Hamano
2021-09-08 16:24 ` Taylor Blau
2021-09-08 19:23 ` Junio C Hamano
2021-09-09 1:02 ` Taylor Blau
2021-09-08 21:27 ` Jeff King
2021-09-08 16:55 ` Azeem Bande-Ali
2021-09-08 19:20 ` Junio C Hamano
2021-09-08 17:50 ` Philippe Blain
2021-09-08 21:57 ` Derrick Stolee
2021-09-09 14:23 ` Elijah Newren
2021-09-09 2:59 ` Ramsay Jones
2021-09-09 17:45 ` Junio C Hamano
2021-09-09 11:03 ` Johannes Schindelin [this message]
2021-09-10 8:52 ` js/scalar, was " Junio C Hamano
2021-09-09 11:05 ` rs/range-diff-avoid-segfault-with-I, " Johannes Schindelin
2021-09-09 11:08 ` js/retire-preserve-merges, " Johannes Schindelin
2021-09-10 5:00 ` Junio C Hamano
2021-09-09 11:08 ` mr/bisect-in-c-4, " Johannes Schindelin
2021-09-10 5:07 ` Junio C Hamano
2021-09-10 9:33 ` Johannes Schindelin
2021-09-09 11:13 ` lh/systemd-timers, " Johannes Schindelin
2021-09-09 11:15 ` ar/submodule-add-more, " Johannes Schindelin
2021-09-10 5:30 ` Junio C Hamano
2021-09-09 11:18 ` Ævar Arnfjörð Bjarmason
2021-09-09 14:12 ` Elijah Newren
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
List information: http://vger.kernel.org/majordomo-info.html
* 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.2109091259310.59@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).