On Fri, Dec 3, 2021 at 5:34 AM Johannes Schindelin via GitGitGadget <gitgitgadget@xxxxxxxxx> wrote: > > tl;dr: This series contributes the core part of the Scalar command to the > Git project. This command provides a convenient way to clone/initialize very > large repositories (think: monorepos). > > Note: This patch series' focus is entirely on Scalar, on choosing sensible > defaults and offering a delightful user experience around working with > monorepos, and not about changing any existing paradigms for contrib/ (even > if catching up on the mail thread is likely to give interested readers that > false impression). > > Changes since v9: > > * The patches to build Scalar and run its tests as part of Git's CI/PR, > have been dropped because a recent unrelated patch series does not > interact well with them. i.e. basically undoing this: ... > Changes since v6: ... > * I added two patches that I had planned on keeping in an add-on patch > series for later, to build and test Scalar as part of the CI. I am still > not 100% certain that it is a good idea to do so already now, but let's > see what the reviewers have to say. ...and returning to the original plan: ... > On top of this patch series, I have lined up a few more: ... > 4. A few patches to optionally build and install scalar as part of a > regular Git install (also teaching git help scalar to find the Scalar > documentation Avoiding the issues and adding the CI later seems reasonable to me. You addressed the last of my points in v9; I think this version is good to go. But one quick comment... > These are included in my vfs-with-scalar branch thicket > [https://github.com/dscho/git/commits/vfs-with-scalar]. On top of that, this > branch thicket also includes patches I do not plan on upstreaming, mainly > because they are too specific either to VFS for Git, or they support Azure > Repos (which does not offer partial clones but speaks the GVFS protocol, > which can be used to emulate partial clones). > > One other thing is very interesting about that vfs-with-scalar branch > thicket: it contains a GitHub workflow which will run Scalar's quite > extensive Functional Tests suite. This test suite is quite comprehensive and > caught us a lot of bugs in the past, not only in the Scalar code, but also > core Git. >From your wording it sounds like the plan might not include moving these tests over. Perhaps it doesn't make sense to move them all over, but since they've caught problems in both Scalar and core Git, it would be nice to see many of those tests come to Git as well as part of a future follow on series.
