diff options
| author | Nguyễn Thái Ngọc Duy <pclouds@gmail.com> | 2018-04-30 17:35:33 +0200 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2018-05-02 10:03:33 +0200 |
| commit | 76a8788c141e9d4e2713acaa7886475fb6b27ca5 (patch) | |
| tree | 39737a2b50579f34e6cbf2b58d905206928bdcf8 /Documentation/git-filter-branch.txt | |
| parent | The fourth batch for 2.18 (diff) | |
| download | git-76a8788c141e9d4e2713acaa7886475fb6b27ca5.tar.xz git-76a8788c141e9d4e2713acaa7886475fb6b27ca5.zip | |
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>
Diffstat (limited to 'Documentation/git-filter-branch.txt')
| -rw-r--r-- | Documentation/git-filter-branch.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt index b634043183..aae0253379 100644 --- a/Documentation/git-filter-branch.txt +++ b/Documentation/git-filter-branch.txt @@ -230,7 +230,7 @@ rewrite, the exit status is `2`. On any other error, the exit status may be any other non-zero value. -Examples +EXAMPLES -------- Suppose you want to remove a file (containing confidential information @@ -406,7 +406,7 @@ git filter-branch --index-filter \ -Checklist for Shrinking a Repository +CHECKLIST FOR SHRINKING A REPOSITORY ------------------------------------ git-filter-branch can be used to get rid of a subset of files, @@ -445,7 +445,7 @@ warned. (or if your git-gc is not new enough to support arguments to `--prune`, use `git repack -ad; git prune` instead). -Notes +NOTES ----- git-filter-branch allows you to make complex shell-scripted rewrites |