aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/technical
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2022-08-25 14:42:32 -0700
committerJunio C Hamano <gitster@pobox.com>2022-08-25 14:42:32 -0700
commitf00ddc9f4861ab126ea48d1551dd7e2ed5f90943 (patch)
treec47af2e86c4b56496951a5fd91892321e15c74eb /Documentation/technical
parenta103ad6f3d58cf3d297a6b102876e2bbf09c98d7 (diff)
parent43370b1e910f767b327046b1c4253c82e9695052 (diff)
downloadgit-f00ddc9f4861ab126ea48d1551dd7e2ed5f90943.tar.gz
Merge branch 'vd/scalar-generalize-diagnose'
The "diagnose" feature to create a zip archive for diagnostic material has been lifted from "scalar" and made into a feature of "git bugreport". * vd/scalar-generalize-diagnose: scalar: update technical doc roadmap scalar-diagnose: use 'git diagnose --mode=all' builtin/bugreport.c: create '--diagnose' option builtin/diagnose.c: add '--mode' option builtin/diagnose.c: create 'git diagnose' builtin diagnose.c: add option to configure archive contents scalar-diagnose: move functionality to common location scalar-diagnose: move 'get_disk_info()' to 'compat/' scalar-diagnose: add directory to archiver more gently scalar-diagnose: avoid 32-bit overflow of size_t scalar-diagnose: use "$GIT_UNZIP" in test
Diffstat (limited to 'Documentation/technical')
-rw-r--r--Documentation/technical/scalar.txt9
1 files changed, 3 insertions, 6 deletions
diff --git a/Documentation/technical/scalar.txt b/Documentation/technical/scalar.txt
index 08bc09c225..f6353375f0 100644
--- a/Documentation/technical/scalar.txt
+++ b/Documentation/technical/scalar.txt
@@ -84,6 +84,9 @@ series have been accepted:
- `scalar-diagnose`: The `scalar` command is taught the `diagnose` subcommand.
+- `scalar-generalize-diagnose`: Move the functionality of `scalar diagnose`
+ into `git diagnose` and `git bugreport --diagnose`.
+
Roughly speaking (and subject to change), the following series are needed to
"finish" this initial version of Scalar:
@@ -91,12 +94,6 @@ Roughly speaking (and subject to change), the following series are needed to
and implement `scalar help`. At the end of this series, Scalar should be
feature-complete from the perspective of a user.
-- Generalize features not specific to Scalar: In the spirit of making Scalar
- configure only what is needed for large repo performance, move common
- utilities into other parts of Git. Some of this will be internal-only, but one
- major change will be generalizing `scalar diagnose` for use with any Git
- repository.
-
- Move Scalar to toplevel: Move Scalar out of `contrib/` and into the root of
`git`, including updates to build and install it with the rest of Git. This
change will incorporate Scalar into the Git CI and test framework, as well as