@@ -143,14 +143,16 @@ include::config/bitmap-pseudo-merge.txt[]
143143Suppose that you have a repository with a large number of references,
144144and you want a bare-bones configuration of pseudo-merge bitmaps that
145145will enhance bitmap coverage of the `refs/` namespace. You may start
146- wiht a configuration like so:
146+ with a configuration like so:
147147
148- [bitmapPseudoMerge "all"]
148+ ----
149+ [bitmapPseudoMerge "all"]
149150 pattern = "refs/"
150151 threshold = now
151152 stableThreshold = never
152153 sampleRate = 100
153154 maxMerges = 64
155+ ----
154156
155157This will create pseudo-merge bitmaps for all references, regardless of
156158their age, and group them into 64 pseudo-merge commits.
@@ -159,21 +161,25 @@ If you wanted to separate tags from branches when generating
159161pseudo-merge commits, you would instead define the pattern with a
160162capture group, like so:
161163
162- [bitmapPseudoMerge "all"]
164+ ----
165+ [bitmapPseudoMerge "all"]
163166 pattern = "refs/(heads/tags)/"
167+ ----
164168
165169Suppose instead that you are working in a fork-network repository, with
166170each fork specified by some numeric ID, and whose refs reside in
167171`refs/virtual/NNN/` (where `NNN` is the numeric ID corresponding to some
168172fork) in the network. In this instance, you may instead write something
169173like:
170174
171- [bitmapPseudoMerge "all"]
175+ ----
176+ [bitmapPseudoMerge "all"]
172177 pattern = "refs/virtual/([0-9]+)/(heads|tags)/"
173178 threshold = now
174179 stableThreshold = never
175180 sampleRate = 100
176181 maxMerges = 64
182+ ----
177183
178184Which would generate pseudo-merge group identifiers like "1234-heads",
179185and "5678-tags" (for branches in fork "1234", and tags in remote "5678",
0 commit comments