@matheusbsbs / matheus-bagliano / commits / 76a8788c14

doc: keep first level section header in upper case

When formatted as a man page, 1st section header is always in upper case even if we write it otherwise. Make all 1st section headers uppercase to keep it close to the final output. This does affect html since case is kept there, but I still think it's a good idea to maintain a consistent style for 1st section headers. Some sections perhaps should become second sections instead, where case is kept, and for better organization. I will update if anyone has suggestions about this. While at there I also make some header more consistent (e.g. examples vs example) and fix a couple minor things here and there. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Nguyễn Thái Ngọc Duy committed Apr 30, 2018 at 17:35 UTC 76a8788c141e9d4e2713acaa7886475fb6b27ca5
38 files changed +96 -96
Documentation/git-add.txt
+2 -2
@@ -193,7 +193,7 @@ for "git add --no-all <pathspec>...", i.e. ignored removed files.
193 for command-line options).
194
195
196 -Configuration
196 +CONFIGURATION
197 -------------
198
199 The optional configuration variable `core.excludesFile` indicates a path to a
@@ -226,7 +226,7 @@ Because this example lets the shell expand the asterisk (i.e. you are
226 listing the files explicitly), it does not consider
227 `subdir/git-foo.sh`.
228
229 -Interactive mode
229 +INTERACTIVE MODE
230 ----------------
231 When the command enters the interactive mode, it shows the
232 output of the 'status' subcommand, and then goes into its
Documentation/git-apply.txt
+2 -2
@@ -240,7 +240,7 @@ When `git apply` is used as a "better GNU patch", the user can pass
240 the `--unsafe-paths` option to override this safety check. This option
241 has no effect when `--index` or `--cached` is in use.
242
243 -Configuration
243 +CONFIGURATION
244 -------------
245
246 apply.ignoreWhitespace::
@@ -251,7 +251,7 @@ apply.whitespace::
251 When no `--whitespace` flag is given from the command
252 line, this configuration item is used as the default.
253
254 -Submodules
254 +SUBMODULES
255 ----------
256 If the patch contains any changes to submodules then 'git apply'
257 treats these changes as follows.
Documentation/git-branch.txt
+2 -2
@@ -287,7 +287,7 @@ CONFIGURATION
287 `--list` is used or implied. The default is to use a pager.
288 See linkgit:git-config[1].
289
290 -Examples
290 +EXAMPLES
291 --------
292
293 Start development from a known tag::
@@ -318,7 +318,7 @@ See linkgit:git-fetch[1].
318 is currently checked out) does not have all commits from the test branch.
319
320
321 -Notes
321 +NOTES
322 -----
323
324 If you are creating a branch that you want to checkout immediately, it is
Documentation/git-bundle.txt
+2 -2
@@ -92,8 +92,8 @@ It is okay to err on the side of caution, causing the bundle file
92 to contain objects already in the destination, as these are ignored
93 when unpacking at the destination.
94
95 -EXAMPLE
96 --------
95 +EXAMPLES
96 +--------
97
98 Assume you want to transfer the history from a repository R1 on machine A
99 to another repository R2 on machine B.
Documentation/git-clone.txt
+1 -1
@@ -273,7 +273,7 @@ or `--mirror` is given)
273 :git-clone: 1
274 include::urls.txt[]
275
276 -Examples
276 +EXAMPLES
277 --------
278
279 * Clone from upstream:
Documentation/git-cvsserver.txt
+5 -5
@@ -207,7 +207,7 @@ allowing access over SSH.
207 ------
208
209 [[dbbackend]]
210 -Database Backend
210 +DATABASE BACKEND
211 ----------------
212
213 'git-cvsserver' uses one database per Git head (i.e. CVS module) to
@@ -321,7 +321,7 @@ git-cvsserver, as described above.
321 When these environment variables are set, the corresponding
322 command-line arguments may not be used.
323
324 -Eclipse CVS Client Notes
324 +ECLIPSE CVS CLIENT NOTES
325 ------------------------
326
327 To get a checkout with the Eclipse CVS client:
@@ -346,7 +346,7 @@ offer. In that case CVS_SERVER is ignored, and you will have to replace
346 the cvs utility on the server with 'git-cvsserver' or manipulate your `.bashrc`
347 so that calling 'cvs' effectively calls 'git-cvsserver'.
348
349 -Clients known to work
349 +CLIENTS KNOWN TO WORK
350 ---------------------
351
352 - CVS 1.12.9 on Debian
@@ -354,7 +354,7 @@ Clients known to work
354 - Eclipse 3.0, 3.1.2 on MacOSX (see Eclipse CVS Client Notes)
355 - TortoiseCVS
356
357 -Operations supported
357 +OPERATIONS SUPPORTED
358 --------------------
359
360 All the operations required for normal use are supported, including
@@ -424,7 +424,7 @@ For best consistency with 'cvs', it is probably best to override the
424 defaults by setting `gitcvs.usecrlfattr` to true,
425 and `gitcvs.allBinary` to "guess".
426
427 -Dependencies
427 +DEPENDENCIES
428 ------------
429 'git-cvsserver' depends on DBD::SQLite.
430
Documentation/git-diff-index.txt
+3 -3
@@ -37,14 +37,14 @@ include::diff-options.txt[]
37
38 include::diff-format.txt[]
39
40 -Operating Modes
40 +OPERATING MODES
41 ---------------
42 You can choose whether you want to trust the index file entirely
43 (using the `--cached` flag) or ask the diff logic to show any files
44 that don't match the stat state as being "tentatively changed". Both
45 of these operations are very useful indeed.
46
47 -Cached Mode
47 +CACHED MODE
48 -----------
49 If `--cached` is specified, it allows you to ask:
50
@@ -77,7 +77,7 @@ So doing a `git diff-index --cached` is basically very useful when you are
77 asking yourself "what have I already marked for being committed, and
78 what's the difference to a previous tree".
79
80 -Non-cached Mode
80 +NON-CACHED MODE
81 ---------------
82 The "non-cached" mode takes a different approach, and is potentially
83 the more useful of the two in that what it does can't be emulated with
Documentation/git-diff-tree.txt
+1 -1
@@ -116,7 +116,7 @@ include::pretty-options.txt[]
116 include::pretty-formats.txt[]
117
118
119 -Limiting Output
119 +LIMITING OUTPUT
120 ---------------
121 If you're only interested in differences in a subset of files, for
122 example some architecture-specific files, you might do:
Documentation/git-fast-export.txt
+1 -1
@@ -202,7 +202,7 @@ smaller output, and it is usually easy to quickly confirm that there is
202 no private data in the stream.
203
204
205 -Limitations
205 +LIMITATIONS
206 -----------
207
208 Since 'git fast-import' cannot tag trees, you will not be
Documentation/git-fast-import.txt
+11 -11
@@ -139,7 +139,7 @@ Performance and Compression Tuning
139 fastimport.unpackLimit::
140 See linkgit:git-config[1]
141
142 -Performance
142 +PERFORMANCE
143 -----------
144 The design of fast-import allows it to import large projects in a minimum
145 amount of memory usage and processing time. Assuming the frontend
@@ -155,7 +155,7 @@ faster if the source data is stored on a different drive than the
155 destination Git repository (due to less IO contention).
156
157
158 -Development Cost
158 +DEVELOPMENT COST
159 ----------------
160 A typical frontend for fast-import tends to weigh in at approximately 200
161 lines of Perl/Python/Ruby code. Most developers have been able to
@@ -165,7 +165,7 @@ an ideal situation, given that most conversion tools are throw-away
165 (use once, and never look back).
166
167
168 -Parallel Operation
168 +PARALLEL OPERATION
169 ------------------
170 Like 'git push' or 'git fetch', imports handled by fast-import are safe to
171 run alongside parallel `git repack -a -d` or `git gc` invocations,
@@ -186,7 +186,7 @@ this only be used on an otherwise quiet repository. Using --force
186 is not necessary for an initial import into an empty repository.
187
188
189 -Technical Discussion
189 +TECHNICAL DISCUSSION
190 --------------------
191 fast-import tracks a set of branches in memory. Any branch can be created
192 or modified at any point during the import process by sending a
@@ -204,7 +204,7 @@ directory also allows fast-import to run very quickly, as it does not
204 need to perform any costly file update operations when switching
205 between branches.
206
207 -Input Format
207 +INPUT FORMAT
208 ------------
209 With the exception of raw file data (which Git does not interpret)
210 the fast-import input format is text (ASCII) based. This text based
@@ -1131,7 +1131,7 @@ If the `--done` command-line option or `feature done` command is
1131 in use, the `done` command is mandatory and marks the end of the
1132 stream.
1133
1134 -Responses To Commands
1134 +RESPONSES TO COMMANDS
1135 ---------------------
1136 New objects written by fast-import are not available immediately.
1137 Most fast-import commands have no visible effect until the next
@@ -1160,7 +1160,7 @@ To avoid deadlock, such frontends must completely consume any
1160 pending output from `progress`, `ls`, `get-mark`, and `cat-blob` before
1161 performing writes to fast-import that might block.
1162
1163 -Crash Reports
1163 +CRASH REPORTS
1164 -------------
1165 If fast-import is supplied invalid input it will terminate with a
1166 non-zero exit status and create a crash report in the top level of
@@ -1247,7 +1247,7 @@ An example crash:
1247 END OF CRASH REPORT
1248 ====
1249
1250 -Tips and Tricks
1250 +TIPS AND TRICKS
1251 ---------------
1252 The following tips and tricks have been collected from various
1253 users of fast-import, and are offered here as suggestions.
@@ -1349,7 +1349,7 @@ Your users will feel better knowing how much of the data stream
1349 has been processed.
1350
1351
1352 -Packfile Optimization
1352 +PACKFILE OPTIMIZATION
1353 ---------------------
1354 When packing a blob fast-import always attempts to deltify against the last
1355 blob written. Unless specifically arranged for by the frontend,
@@ -1380,7 +1380,7 @@ to force recomputation of all deltas can significantly reduce the
1380 final packfile size (30-50% smaller can be quite typical).
1381
1382
1383 -Memory Utilization
1383 +MEMORY UTILIZATION
1384 ------------------
1385 There are a number of factors which affect how much memory fast-import
1386 requires to perform an import. Like critical sections of core
@@ -1458,7 +1458,7 @@ and lazy loading of subtrees, allows fast-import to efficiently import
1458 projects with 2,000+ branches and 45,114+ files in a very limited
1459 memory footprint (less than 2.7 MiB per active branch).
1460
1461 -Signals
1461 +SIGNALS
1462 -------
1463 Sending *SIGUSR1* to the 'git fast-import' process ends the current
1464 packfile early, simulating a `checkpoint` command. The impatient
Documentation/git-filter-branch.txt
+3 -3
@@ -230,7 +230,7 @@ rewrite, the exit status is `2`. On any other error, the exit status may be
230 any other non-zero value.
231
232
233 -Examples
233 +EXAMPLES
234 --------
235
236 Suppose you want to remove a file (containing confidential information
@@ -406,7 +406,7 @@ git filter-branch --index-filter \
406
407
408
409 -Checklist for Shrinking a Repository
409 +CHECKLIST FOR SHRINKING A REPOSITORY
410 ------------------------------------
411
412 git-filter-branch can be used to get rid of a subset of files,
@@ -445,7 +445,7 @@ warned.
445 (or if your git-gc is not new enough to support arguments to
446 `--prune`, use `git repack -ad; git prune` instead).
447
448 -Notes
448 +NOTES
449 -----
450
451 git-filter-branch allows you to make complex shell-scripted rewrites
Documentation/git-fmt-merge-msg.txt
+2 -2
@@ -57,8 +57,8 @@ merge.summary::
57 Synonym to `merge.log`; this is deprecated and will be removed in
58 the future.
59
60 -EXAMPLE
61 --------
60 +EXAMPLES
61 +--------
62
63 ---------
64 $ git fetch origin master
Documentation/git-gc.txt
+2 -2
@@ -84,7 +84,7 @@ be performed as well.
84 Force `git gc` to run even if there may be another `git gc`
85 instance running on this repository.
86
87 -Configuration
87 +CONFIGURATION
88 -------------
89
90 The optional configuration variable `gc.reflogExpire` can be
@@ -144,7 +144,7 @@ old a stale working tree should be before `git worktree prune` deletes
144 it. Default is "3 months ago".
145
146
147 -Notes
147 +NOTES
148 -----
149
150 'git gc' tries very hard not to delete objects that are referenced
Documentation/git-grep.txt
+1 -1
@@ -293,7 +293,7 @@ providing this option will cause it to die.
293 For more details about the <pathspec> syntax, see the 'pathspec' entry
294 in linkgit:gitglossary[7].
295
296 -Examples
296 +EXAMPLES
297 --------
298
299 `git grep 'time_t' -- '*.[ch]'`::
Documentation/git-http-push.txt
+1 -1
@@ -55,7 +55,7 @@ OPTIONS
55 The remote refs to update.
56
57
58 -Specifying the Refs
58 +SPECIFYING THE REFS
59 -------------------
60
61 A '<ref>' specification can be either a single pattern, or a pair
Documentation/git-imap-send.txt
+2 -2
@@ -136,8 +136,8 @@ Using direct mode with SSL:
136 .........................
137
138
139 -EXAMPLE
140 --------
139 +EXAMPLES
140 +--------
141 To submit patches using GMail's IMAP interface, first, edit your ~/.gitconfig
142 to specify your account settings:
143
Documentation/git-index-pack.txt
+2 -2
@@ -93,8 +93,8 @@ OPTIONS
93 --max-input-size=<size>::
94 Die, if the pack is larger than <size>.
95
96 -Note
97 -----
96 +NOTES
97 +-----
98
99 Once the index has been created, the list of object names is sorted
100 and the SHA-1 hash of that list is printed to stdout. If --stdin was
Documentation/git-ls-files.txt
+2 -2
@@ -183,7 +183,7 @@ followed by the ("attr/<eolattr>").
183 Files to show. If no files are given all files which match the other
184 specified criteria are shown.
185
186 -Output
186 +OUTPUT
187 ------
188 'git ls-files' just outputs the filenames unless `--stage` is specified in
189 which case it outputs:
@@ -208,7 +208,7 @@ quoted as explained for the configuration variable `core.quotePath`
208 verbatim and the line is terminated by a NUL byte.
209
210
211 -Exclude Patterns
211 +EXCLUDE PATTERNS
212 ----------------
213
214 'git ls-files' can use a list of "exclude patterns" when
Documentation/git-name-rev.txt
+2 -2
@@ -61,8 +61,8 @@ OPTIONS
61 --always::
62 Show uniquely abbreviated commit object as fallback.
63
64 -EXAMPLE
65 --------
64 +EXAMPLES
65 +--------
66
67 Given a commit, find out where it is relative to the local refs. Say somebody
68 wrote you about that fantastic commit 33db5f4d9027a10e477ccf054b2c1ab94f74c85a.
Documentation/git-p4.txt
+2 -2
@@ -29,8 +29,8 @@ Submit Git changes back to p4 using 'git p4 submit'. The command
29 the updated p4 remote branch.
30
31
32 -EXAMPLE
33 --------
32 +EXAMPLES
33 +--------
34 * Clone a repository:
35 +
36 ------------
Documentation/git-prune.txt
+3 -3
@@ -56,8 +56,8 @@ OPTIONS
56 reachable from any of our references, keep objects
57 reachable from listed <head>s.
58
59 -EXAMPLE
60 --------
59 +EXAMPLES
60 +--------
61
62 To prune objects not used by your repository or another that
63 borrows from your repository via its
@@ -67,7 +67,7 @@ borrows from your repository via its
67 $ git prune $(cd ../another && git rev-parse --all)
68 ------------
69
70 -Notes
70 +NOTES
71 -----
72
73 In most cases, users will not need to call 'git prune' directly, but
Documentation/git-push.txt
+2 -2
@@ -423,7 +423,7 @@ reason::
423 refs, no explanation is needed. For a failed ref, the reason for
424 failure is described.
425
426 -Note about fast-forwards
426 +NOTE ABOUT FAST-FORWARDS
427 ------------------------
428
429 When an update changes a branch (or more in general, a ref) that used to
@@ -510,7 +510,7 @@ overwrite it. In other words, "git push --force" is a method reserved for
510 a case where you do mean to lose history.
511
512
513 -Examples
513 +EXAMPLES
514 --------
515
516 `git push`::
Documentation/git-read-tree.txt
+2 -2
@@ -132,7 +132,7 @@ OPTIONS
132 The id of the tree object(s) to be read/merged.
133
134
135 -Merging
135 +MERGING
136 -------
137 If `-m` is specified, 'git read-tree' can perform 3 kinds of
138 merge, a single tree merge if only 1 tree is given, a
@@ -382,7 +382,7 @@ middle of doing, and when your working tree is ready (i.e. you
382 have finished your work-in-progress), attempt the merge again.
383
384
385 -Sparse checkout
385 +SPARSE CHECKOUT
386 ---------------
387
388 "Sparse checkout" allows populating the working directory sparsely.
Documentation/git-receive-pack.txt
+5 -5
@@ -41,7 +41,7 @@ OPTIONS
41 <directory>::
42 The repository to sync into.
43
44 -pre-receive Hook
44 +PRE-RECEIVE HOOK
45 ----------------
46 Before any ref is updated, if $GIT_DIR/hooks/pre-receive file exists
47 and is executable, it will be invoked once with no parameters. The
@@ -116,7 +116,7 @@ bail out if the update is not to be supported.
116
117 See the notes on the quarantine environment below.
118
119 -update Hook
119 +UPDATE HOOK
120 -----------
121 Before each ref is updated, if $GIT_DIR/hooks/update file exists
122 and is executable, it is invoked once per ref, with three parameters:
@@ -138,7 +138,7 @@ ensure the ref will actually be updated, it is only a prerequisite.
138 As such it is not a good idea to send notices (e.g. email) from
139 this hook. Consider using the post-receive hook instead.
140
141 -post-receive Hook
141 +POST-RECEIVE HOOK
142 -----------------
143 After all refs were updated (or attempted to be updated), if any
144 ref update was successful, and if $GIT_DIR/hooks/post-receive
@@ -198,7 +198,7 @@ after it was updated by 'git-receive-pack', but before the hook was able
198 to evaluate it. It is recommended that hooks rely on sha1-new
199 rather than the current value of refname.
200
201 -post-update Hook
201 +POST-UPDATE HOOK
202 ----------------
203 After all other processing, if at least one ref was updated, and
204 if $GIT_DIR/hooks/post-update file exists and is executable, then
@@ -216,7 +216,7 @@ if the repository is packed and is served via a dumb transport.
216 exec git update-server-info
217
218
219 -Quarantine Environment
219 +QUARANTINE ENVIRONMENT
220 ----------------------
221
222 When `receive-pack` takes in objects, they are placed into a temporary
Documentation/git-remote-ext.txt
+6 -6
@@ -55,14 +55,14 @@ some tunnel.
55 the vhost field in the git:// service request (to rest of the argument).
56 Default is not to send vhost in such request (if sent).
57
58 -ENVIRONMENT VARIABLES:
59 -----------------------
58 +ENVIRONMENT VARIABLES
59 +---------------------
60
61 GIT_TRANSLOOP_DEBUG::
62 If set, prints debugging information about various reads/writes.
63
64 -ENVIRONMENT VARIABLES PASSED TO COMMAND:
65 -----------------------------------------
64 +ENVIRONMENT VARIABLES PASSED TO COMMAND
65 +---------------------------------------
66
67 GIT_EXT_SERVICE::
68 Set to long name (git-upload-pack, etc...) of service helper needs
@@ -73,8 +73,8 @@ GIT_EXT_SERVICE_NOPREFIX::
73 to invoke.
74
75
76 -EXAMPLES:
77 ----------
76 +EXAMPLES
77 +--------
78 This remote helper is transparently used by Git when
79 you use commands such as "git fetch <URL>", "git clone <URL>",
80 , "git push <URL>" or "git remote add <nick> <URL>", where <URL>
Documentation/git-remote.txt
+1 -1
@@ -203,7 +203,7 @@ The remote configuration is achieved using the `remote.origin.url` and
203 `remote.origin.fetch` configuration variables. (See
204 linkgit:git-config[1]).
205
206 -Examples
206 +EXAMPLES
207 --------
208
209 * Add a new remote, fetch, and check out a branch from it
Documentation/git-request-pull.txt
+2 -2
@@ -46,8 +46,8 @@ ref that is different from the ref you have locally, you can use the
46 its remote name.
47
48
49 -EXAMPLE
50 --------
49 +EXAMPLES
50 +--------
51
52 Imagine that you built your work on your `master` branch on top of
53 the `v1.0` release, and want it to be integrated to the project.
Documentation/git-send-email.txt
+2 -2
@@ -458,8 +458,8 @@ sendemail.confirm::
458 one of 'always', 'never', 'cc', 'compose', or 'auto'. See `--confirm`
459 in the previous section for the meaning of these values.
460
461 -EXAMPLE
462 --------
461 +EXAMPLES
462 +--------
463 Use gmail as the smtp server
464 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
465 To use 'git send-email' to send your patches through the GMail SMTP server,
Documentation/git-send-pack.txt
+1 -1
@@ -99,7 +99,7 @@ be in a separate packet, and the list must end with a flush packet.
99 The remote refs to update.
100
101
102 -Specifying the Refs
102 +SPECIFYING THE REFS
103 -------------------
104
105 There are three ways to specify which refs to update on the
Documentation/git-shell.txt
+2 -2
@@ -62,8 +62,8 @@ permissions.
62 If a `no-interactive-login` command exists, then it is run and the
63 interactive shell is aborted.
64
65 -EXAMPLE
66 --------
65 +EXAMPLES
66 +--------
67
68 To disable interactive logins, displaying a greeting instead:
69
Documentation/git-show-branch.txt
+2 -2
@@ -173,8 +173,8 @@ The "fixes" branch adds one commit "Introduce "reset type" flag to
173 The current branch is "master".
174
175
176 -EXAMPLE
177 --------
176 +EXAMPLES
177 +--------
178
179 If you keep your primary branches immediately under
180 `refs/heads`, and topic branches in subdirectories of
Documentation/git-show-ref.txt
+2 -2
@@ -120,8 +120,8 @@ $ git show-ref --heads --hash
120 ...
121 -----------------------------------------------------------------------------
122
123 -EXAMPLE
124 --------
123 +EXAMPLES
124 +--------
125
126 To show all references called "master", whether tags or heads or anything
127 else, and regardless of how deep in the reference naming hierarchy they are,
Documentation/git-show.txt
+1 -1
@@ -77,7 +77,7 @@ EXAMPLES
77 Concatenates the contents of said Makefiles in the head
78 of the branch `master`.
79
80 -Discussion
80 +DISCUSSION
81 ----------
82
83 include::i18n.txt[]
Documentation/git-update-index.txt
+10 -10
@@ -228,7 +228,7 @@ will remove the intended effect of the option.
228 cleaner names.
229 The same applies to directories ending '/' and paths with '//'
230
231 -Using --refresh
231 +USING --REFRESH
232 ---------------
233 `--refresh` does not calculate a new sha1 file or bring the index
234 up to date for mode/content changes. But what it *does* do is to
@@ -239,7 +239,7 @@ the stat entry is out of date.
239 For example, you'd want to do this after doing a 'git read-tree', to link
240 up the stat index details with the proper files.
241
242 -Using --cacheinfo or --info-only
242 +USING --CACHEINFO OR --INFO-ONLY
243 --------------------------------
244 `--cacheinfo` is used to register a file that is not in the
245 current working directory. This is useful for minimum-checkout
@@ -261,7 +261,7 @@ useful when the file is available, but you do not wish to update the
261 object database.
262
263
264 -Using --index-info
264 +USING --INDEX-INFO
265 ------------------
266
267 `--index-info` is a more powerful mechanism that lets you feed
@@ -317,7 +317,7 @@ $ git ls-files -s
317 ------------
318
319
320 -Using ``assume unchanged'' bit
320 +USING ``ASSUME UNCHANGED'' BIT
321 ------------------------------
322
323 Many operations in Git depend on your filesystem to have an
@@ -350,7 +350,7 @@ the index (use `git update-index --really-refresh` if you want
350 to mark them as "assume unchanged").
351
352
353 -Examples
353 +EXAMPLES
354 --------
355 To update and refresh only the files already checked out:
356
@@ -387,7 +387,7 @@ M foo.c
387 <9> now it checks with lstat(2) and finds it has been changed.
388
389
390 -Skip-worktree bit
390 +SKIP-WORKTREE BIT
391 -----------------
392
393 Skip-worktree bit can be defined in one (long) sentence: When reading
@@ -407,7 +407,7 @@ Although this bit looks similar to assume-unchanged bit, its goal is
407 different from assume-unchanged bit's. Skip-worktree also takes
408 precedence over assume-unchanged bit when both are set.
409
410 -Split index
410 +SPLIT INDEX
411 -----------
412
413 This mode is designed for repositories with very large indexes, and
@@ -432,7 +432,7 @@ To avoid deleting a shared index file that is still used, its
432 modification time is updated to the current time everytime a new split
433 index based on the shared index file is either created or read from.
434
435 -Untracked cache
435 +UNTRACKED CACHE
436 ---------------
437
438 This cache is meant to speed up commands that involve determining
@@ -490,7 +490,7 @@ As with the bug described above the solution is to one-off do a "git
490 status" run with `core.untrackedCache=false` to flush out the leftover
491 bad data.
492
493 -File System Monitor
493 +FILE SYSTEM MONITOR
494 -------------------
495
496 This feature is intended to speed up git operations for repos that have
@@ -518,7 +518,7 @@ file system monitor is added to or removed from the index the next time
518 a command reads the index. When `--[no-]fsmonitor` are used, the file
519 system monitor is immediately added to or removed from the index.
520
521 -Configuration
521 +CONFIGURATION
522 -------------
523
524 The command honors `core.filemode` configuration variable. If
Documentation/git-update-ref.txt
+1 -1
@@ -120,7 +120,7 @@ modifications are performed. Note that while each individual
120 <ref> is updated or deleted atomically, a concurrent reader may
121 still see a subset of the modifications.
122
123 -Logging Updates
123 +LOGGING UPDATES
124 ---------------
125 If config parameter "core.logAllRefUpdates" is true and the ref is one under
126 "refs/heads/", "refs/remotes/", "refs/notes/", or the symbolic ref HEAD; or
Documentation/git-var.txt
+2 -2
@@ -23,14 +23,14 @@ OPTIONS
23 as well. (However, the configuration variables listing functionality
24 is deprecated in favor of `git config -l`.)
25
26 -EXAMPLE
26 +EXAMPLES
27 --------
28 $ git var GIT_AUTHOR_IDENT
29 Eric W. Biederman <ebiederm@lnxi.com> 1121223278 -0600
30
31
32 VARIABLES
33 -----------
33 +---------
34 GIT_AUTHOR_IDENT::
35 The author of a piece of code.
36
Documentation/git-web--browse.txt
+1 -1
@@ -84,7 +84,7 @@ variable exists then 'git web{litdd}browse' will treat the specified tool
84 as a custom command and will use a shell eval to run the command with
85 the URLs passed as arguments.
86
87 -Note about konqueror
87 +NOTE ABOUT KONQUEROR
88 --------------------
89
90 When 'konqueror' is specified by a command-line option or a
Documentation/gitattributes.txt
+2 -2
@@ -1141,8 +1141,8 @@ to:
1141 ------------
1142
1143
1144 -EXAMPLE
1145 --------
1144 +EXAMPLES
1145 +--------
1146
1147 If you have these three `gitattributes` file:
1148