Gecko [ www.satitravel.com ]

Name	Size	Permission	Date
api-error-handling.html	21.74 KB	-rw-r--r--	2025-07-22 14:31
api-error-handling.txt	3.73 KB	-rw-r--r--	2025-06-13 22:14
api-index-skel.txt	432 B	-rw-r--r--	2025-06-13 22:14
api-index.html	16.78 KB	-rw-r--r--	2025-07-22 14:32
api-index.sh	611 B	-rw-r--r--	2025-06-13 22:14
api-index.txt	648 B	-rw-r--r--	2025-07-22 14:31
api-merge.html	17.88 KB	-rw-r--r--	2025-07-22 14:31
api-merge.txt	1.06 KB	-rw-r--r--	2025-06-13 22:14
api-parse-options.html	35.8 KB	-rw-r--r--	2025-07-22 14:31
api-parse-options.txt	12.85 KB	-rw-r--r--	2025-06-13 22:14
api-simple-ipc.html	21.86 KB	-rw-r--r--	2025-07-22 14:30
api-simple-ipc.txt	4.74 KB	-rw-r--r--	2025-06-13 22:14
api-trace2.html	75.8 KB	-rw-r--r--	2025-07-22 14:31
api-trace2.txt	43.22 KB	-rw-r--r--	2025-06-13 22:14
bitmap-format.html	29.69 KB	-rw-r--r--	2025-07-22 14:31
bitmap-format.txt	8.66 KB	-rw-r--r--	2025-06-13 22:14
bundle-uri.html	50.18 KB	-rw-r--r--	2025-07-22 14:31
bundle-uri.txt	26.16 KB	-rw-r--r--	2025-06-13 22:14
commit-graph.txt	17.54 KB	-rw-r--r--	2025-06-13 22:14
directory-rename-detection.txt	5.08 KB	-rw-r--r--	2025-06-13 22:14
hash-function-transition.html	63.03 KB	-rw-r--r--	2025-07-22 14:31
hash-function-transition.txt	35.05 KB	-rw-r--r--	2025-06-13 22:14
long-running-process-protocol.html	18.55 KB	-rw-r--r--	2025-07-22 14:31
long-running-process-protocol.txt	1.88 KB	-rw-r--r--	2025-06-13 22:14
multi-pack-index.html	21.94 KB	-rw-r--r--	2025-07-22 14:31
multi-pack-index.txt	4.35 KB	-rw-r--r--	2025-06-13 22:14
pack-heuristics.html	42.57 KB	-rw-r--r--	2025-07-22 14:31
pack-heuristics.txt	17.62 KB	-rw-r--r--	2025-06-13 22:14
packfile-uri.txt	3.66 KB	-rw-r--r--	2025-06-13 22:14
parallel-checkout.html	30.97 KB	-rw-r--r--	2025-07-22 14:31
parallel-checkout.txt	12.01 KB	-rw-r--r--	2025-06-13 22:14
partial-clone.html	35.64 KB	-rw-r--r--	2025-07-22 14:31
partial-clone.txt	14.62 KB	-rw-r--r--	2025-06-13 22:14
racy-git.html	27.34 KB	-rw-r--r--	2025-07-22 14:31
racy-git.txt	8.91 KB	-rw-r--r--	2025-06-13 22:14
reftable.html	72.06 KB	-rw-r--r--	2025-07-22 14:31
reftable.txt	36.65 KB	-rw-r--r--	2025-06-13 22:14
remembering-renames.txt	29.65 KB	-rw-r--r--	2025-06-13 22:14
repository-version.txt	4.21 KB	-rw-r--r--	2025-06-13 22:14
rerere.txt	6.36 KB	-rw-r--r--	2025-06-13 22:14
scalar.html	19.98 KB	-rw-r--r--	2025-07-22 14:31
scalar.txt	2.87 KB	-rw-r--r--	2025-06-13 22:14
send-pack-pipeline.html	18.86 KB	-rw-r--r--	2025-07-22 14:31
send-pack-pipeline.txt	1.92 KB	-rw-r--r--	2025-06-13 22:14
shallow.html	19.22 KB	-rw-r--r--	2025-07-22 14:31
shallow.txt	2.49 KB	-rw-r--r--	2025-06-13 22:14
sparse-checkout.txt	46.39 KB	-rw-r--r--	2025-06-13 22:14
sparse-index.txt	9.28 KB	-rw-r--r--	2025-06-13 22:14
trivial-merge.html	21.75 KB	-rw-r--r--	2025-07-22 14:31
trivial-merge.txt	4.16 KB	-rw-r--r--	2025-06-13 22:14

Rename

Scalar
======

Scalar is a repository management tool that optimizes Git for use in large
repositories. It accomplishes this by helping users to take advantage of
advanced performance features in Git. Unlike most other Git built-in commands,
Scalar is not executed as a subcommand of 'git'; rather, it is built as a
separate executable containing its own series of subcommands.

Background
----------

Scalar was originally designed as an add-on to Git and implemented as a .NET
Core application. It was created based on the learnings from the VFS for Git
project (another application aimed at improving the experience of working with
large repositories). As part of its initial implementation, Scalar relied on
custom features in the Microsoft fork of Git that have since been integrated
into core Git:

* partial clone,
* commit graphs,
* multi-pack index,
* sparse checkout (cone mode),
* scheduled background maintenance,
* etc

With the requisite Git functionality in place and a desire to bring the benefits
of Scalar to the larger Git community, the Scalar application itself was ported
from C# to C and integrated upstream.

Features
--------

Scalar is comprised of two major pieces of functionality: automatically
configuring built-in Git performance features and managing repository
enlistments.

The Git performance features configured by Scalar (see "Background" for
examples) confer substantial performance benefits to large repositories, but are
either too experimental to enable for all of Git yet, or only benefit large
repositories. As new features are introduced, Scalar should be updated
accordingly to incorporate them. This will prevent the tool from becoming stale
while also providing a path for more easily bringing features to the appropriate
users.

Enlistments are how Scalar knows which repositories on a user's system should
utilize Scalar-configured features. This allows it to update performance
settings when new ones are added to the tool, as well as centrally manage
repository maintenance. The enlistment structure - a root directory with a
`src/` subdirectory containing the cloned repository itself - is designed to
encourage users to route build outputs outside of the repository to avoid the
performance-limiting overhead of ignoring those files in Git.

Design
------

Scalar is implemented in C and interacts with Git via a mix of child process
invocations of Git and direct usage of `libgit.a`. Internally, it is structured
much like other built-ins with subcommands (e.g., `git stash`), containing a
`cmd_<subcommand>()` function for each subcommand, routed through a `cmd_main()`
function. Most options are unique to each subcommand, with `scalar` respecting
some "global" `git` options (e.g., `-c` and `-C`).

Because `scalar` is not invoked as a Git subcommand (like `git scalar`), it is
built and installed as its own executable in the `bin/` directory, alongside
`git`, `git-gui`, etc.