@@ -143,14 +143,16 @@ include::config/bitmap-pseudo-merge.txt[]
143
143
Suppose that you have a repository with a large number of references,
144
144
and you want a bare-bones configuration of pseudo-merge bitmaps that
145
145
will enhance bitmap coverage of the `refs/` namespace. You may start
146
- wiht a configuration like so:
146
+ with a configuration like so:
147
147
148
- [bitmapPseudoMerge "all"]
148
+ ----
149
+ [bitmapPseudoMerge "all"]
149
150
pattern = "refs/"
150
151
threshold = now
151
152
stableThreshold = never
152
153
sampleRate = 100
153
154
maxMerges = 64
155
+ ----
154
156
155
157
This will create pseudo-merge bitmaps for all references, regardless of
156
158
their age, and group them into 64 pseudo-merge commits.
@@ -159,21 +161,25 @@ If you wanted to separate tags from branches when generating
159
161
pseudo-merge commits, you would instead define the pattern with a
160
162
capture group, like so:
161
163
162
- [bitmapPseudoMerge "all"]
164
+ ----
165
+ [bitmapPseudoMerge "all"]
163
166
pattern = "refs/(heads/tags)/"
167
+ ----
164
168
165
169
Suppose instead that you are working in a fork-network repository, with
166
170
each fork specified by some numeric ID, and whose refs reside in
167
171
`refs/virtual/NNN/` (where `NNN` is the numeric ID corresponding to some
168
172
fork) in the network. In this instance, you may instead write something
169
173
like:
170
174
171
- [bitmapPseudoMerge "all"]
175
+ ----
176
+ [bitmapPseudoMerge "all"]
172
177
pattern = "refs/virtual/([0-9]+)/(heads|tags)/"
173
178
threshold = now
174
179
stableThreshold = never
175
180
sampleRate = 100
176
181
maxMerges = 64
182
+ ----
177
183
178
184
Which would generate pseudo-merge group identifiers like "1234-heads",
179
185
and "5678-tags" (for branches in fork "1234", and tags in remote "5678",
0 commit comments