Skip to content

Commit

Permalink
Fix formatting in git-config(1)
Browse files Browse the repository at this point in the history
This fixes two formatting bugs in the git-config documentation:

- in the column.ui entry don't indent the last paragraph so that it isn't
  formatted as a literal paragraph
- in the push.default entry separate the last paragraph from the
  nested list.

Signed-off-by: Andreas Schwab <schwab@linux-m68k.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
andreas-schwab authored and gitster committed Jul 3, 2012
1 parent 7260167 commit b129051
Showing 1 changed file with 9 additions and 7 deletions.
16 changes: 9 additions & 7 deletions Documentation/config.txt
Expand Up @@ -881,7 +881,7 @@ column.ui::
make equal size columns
--
+
This option defaults to 'never'.
This option defaults to 'never'.

column.branch::
Specify whether to output branch listing in `git branch` in columns.
Expand Down Expand Up @@ -1721,6 +1721,7 @@ push.default::
no refspec is implied by any of the options given on the command
line. Possible values are:
+
--
* `nothing` - do not push anything.
* `matching` - push all branches having the same name in both ends.
This is for those who prepare all the branches into a publishable
Expand All @@ -1740,12 +1741,13 @@ push.default::
option and is well-suited for beginners. It will become the default
in Git 2.0.
* `current` - push the current branch to a branch of the same name.
+
The `simple`, `current` and `upstream` modes are for those who want to
push out a single branch after finishing work, even when the other
branches are not yet ready to be pushed out. If you are working with
other people to push into the same shared repository, you would want
to use one of these.
--
+
The `simple`, `current` and `upstream` modes are for those who want to
push out a single branch after finishing work, even when the other
branches are not yet ready to be pushed out. If you are working with
other people to push into the same shared repository, you would want
to use one of these.

rebase.stat::
Whether to show a diffstat of what changed upstream since the last
Expand Down

0 comments on commit b129051

Please sign in to comment.