| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
As opposed to the regular CAS/cache, for the git repository implicit
in the repository cache we cannot guarantee that data from older
generation is always promoted via hard links. Therefore, a certain
amount of data can be duplicated between the repo-cache generations.
In order to allow compacting storage to the minimum, add an option
to gc-repo to only remove the older generation, without rotating.
|
|
|
|
|
|
...since it is superseded by ServeApi's method.
|
|
|
|
...instead of EnsureAbsentRootOnServe.
|
|
|
|
...instead of EnsureAbsentRootOnServe.
And remove unused arguments.
|
|
|
|
...instead of EnsureAbsentRootOnServe.
|
|
|
|
...instead of EnsureAbsentRootOnServe
|
|
|
|
|
|
|
|
|
|
|
|
...which implicitly also enforces non-absolute.
This ensures that there is no access outside the root directory of
a Git checkout or the temporary unpack directory of an archive.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
...and access internal state via getters.
|
|
|
|
|
|
|
|
|
|
...and process their bindings.
|
|
...and remove the second for-loop.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
