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
