summaryrefslogtreecommitdiff
path: root/t/t5100/info0014--scissors
diff options
context:
space:
mode:
authorLibravatar Ævar Arnfjörð Bjarmason <avarab@gmail.com>2018-10-10 19:38:18 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-10-11 15:40:27 +0900
commitc7e8ce6d1dd02f6569ea785eebc8692e8e2edf72 (patch)
tree17e91fedbc545c3103a95b178c3e5101e8b101dd /t/t5100/info0014--scissors
parentThird batch for 2.20 (diff)
downloadtgif-c7e8ce6d1dd02f6569ea785eebc8692e8e2edf72.tar.xz
gc doc: mention the commit-graph in the intro
Explicitly mention in the intro that we may be writing supplemental data structures such as the commit-graph during "gc", i.e. to call out the "optimize" part of what this command does, it doesn't just "collect garbage" as the "gc" name might imply. Past changes have updated the intro to reflect new commands, such as mentioning "worktree" in b586a96a39 ("gc.txt: more details about what gc does", 2018-03-15). So let's elaborate on what was added in d5d5d7b641 ("gc: automatically write commit-graph files", 2018-06-27). See also https://public-inbox.org/git/87tvm3go42.fsf@evledraar.gmail.com/ (follow-up replies) for an on-list discussion about what "gc" does. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5100/info0014--scissors')
0 files changed, 0 insertions, 0 deletions