mirrors/git
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation/gitpacking: make sample configs listing blocks

Browse Source 
This document contains a few sample config snippets. At least with
Asciidoctor, the section headers are rendered *more* indented than the
variables that follow:

       [bitmapPseudoMerge "all"]
    pattern = "refs/"
    ...

To address this, wrap these listings in AsciiDoc listing blocks. Remove
the indentation from the section headings. This is similar to how we
handle such sample config elsewhere, e.g., in config.txt.

While we're here, fix the nearby "wiht" typo.

Signed-off-by: Martin Ågren <martin.agren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Martin Ågren
2024-07-17 12:54:28 +02:00
committed by Junio C Hamano
parent a83e21de6b
commit df8b05672c
1 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
Documentation/gitpacking.txt
View File

@ -143,14 +143,16 @@ include::config/bitmap-pseudo-merge.txt[]
Suppose that you have a repository with a large number of references, Suppose that you have a repository with a large number of references,
and you want a bare-bones configuration of pseudo-merge bitmaps that and you want a bare-bones configuration of pseudo-merge bitmaps that
will enhance bitmap coverage of the `refs/` namespace. You may start will enhance bitmap coverage of the `refs/` namespace. You may start
wiht a configuration like so: with a configuration like so:
[bitmapPseudoMerge "all"] ----
[bitmapPseudoMerge "all"]
pattern = "refs/" pattern = "refs/"
threshold = now threshold = now
stableThreshold = never stableThreshold = never
sampleRate = 100 sampleRate = 100
maxMerges = 64 maxMerges = 64
----
This will create pseudo-merge bitmaps for all references, regardless of This will create pseudo-merge bitmaps for all references, regardless of
their age, and group them into 64 pseudo-merge commits. their age, and group them into 64 pseudo-merge commits.
@ -159,8 +161,10 @@ If you wanted to separate tags from branches when generating
pseudo-merge commits, you would instead define the pattern with a pseudo-merge commits, you would instead define the pattern with a
capture group, like so: capture group, like so:
[bitmapPseudoMerge "all"] ----
[bitmapPseudoMerge "all"]
pattern = "refs/(heads/tags)/" pattern = "refs/(heads/tags)/"
----
Suppose instead that you are working in a fork-network repository, with Suppose instead that you are working in a fork-network repository, with
each fork specified by some numeric ID, and whose refs reside in each fork specified by some numeric ID, and whose refs reside in
@ -168,12 +172,14 @@ each fork specified by some numeric ID, and whose refs reside in
fork) in the network. In this instance, you may instead write something fork) in the network. In this instance, you may instead write something
like: like:
[bitmapPseudoMerge "all"] ----
[bitmapPseudoMerge "all"]
pattern = "refs/virtual/([0-9]+)/(heads|tags)/" pattern = "refs/virtual/([0-9]+)/(heads|tags)/"
threshold = now threshold = now
stableThreshold = never stableThreshold = never
sampleRate = 100 sampleRate = 100
maxMerges = 64 maxMerges = 64
----
Which would generate pseudo-merge group identifiers like "1234-heads", Which would generate pseudo-merge group identifiers like "1234-heads",
and "5678-tags" (for branches in fork "1234", and tags in remote "5678", and "5678-tags" (for branches in fork "1234", and tags in remote "5678",