Fix formatting in git-config(1)

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>
This commit is contained in:
Andreas Schwab 2012-06-23 15:18:00 +02:00 коммит произвёл Junio C Hamano
Родитель 726016725d
Коммит b12905140a
1 изменённых файлов: 9 добавлений и 7 удалений

Просмотреть файл

@ -881,7 +881,7 @@ column.ui::
make equal size columns make equal size columns
-- --
+ +
This option defaults to 'never'. This option defaults to 'never'.
column.branch:: column.branch::
Specify whether to output branch listing in `git branch` in columns. Specify whether to output branch listing in `git branch` in columns.
@ -1721,6 +1721,7 @@ push.default::
no refspec is implied by any of the options given on the command no refspec is implied by any of the options given on the command
line. Possible values are: line. Possible values are:
+ +
--
* `nothing` - do not push anything. * `nothing` - do not push anything.
* `matching` - push all branches having the same name in both ends. * `matching` - push all branches having the same name in both ends.
This is for those who prepare all the branches into a publishable This is for those who prepare all the branches into a publishable
@ -1740,12 +1741,13 @@ push.default::
option and is well-suited for beginners. It will become the default option and is well-suited for beginners. It will become the default
in Git 2.0. in Git 2.0.
* `current` - push the current branch to a branch of the same name. * `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 The `simple`, `current` and `upstream` modes are for those who want to
branches are not yet ready to be pushed out. If you are working with push out a single branch after finishing work, even when the other
other people to push into the same shared repository, you would want branches are not yet ready to be pushed out. If you are working with
to use one of these. other people to push into the same shared repository, you would want
to use one of these.
rebase.stat:: rebase.stat::
Whether to show a diffstat of what changed upstream since the last Whether to show a diffstat of what changed upstream since the last