Re: [PATCH 1/2] gitfaq: cleanup gitfaq.txt

[Junio C Hamano <gitster@pobox.com>]

Shourya Shukla <shouryashukla.oo@gmail.com> writes:

> The file contained a lot of whitespace errors as well as some
> grammatical mistakes. Amend them.
>
> Signed-off-by: Shourya Shukla <shouryashukla.oo@gmail.com>
> ---
>  Documentation/gitfaq.txt | 110 +++++++++++++++++++--------------------
>  1 file changed, 55 insertions(+), 55 deletions(-)
>
> diff --git a/Documentation/gitfaq.txt b/Documentation/gitfaq.txt
> index 1cf83df118..3ca16b1092 100644
> --- a/Documentation/gitfaq.txt
> +++ b/Documentation/gitfaq.txt
> @@ -23,7 +23,7 @@ Configuration
>  What should I put in `user.name`?::
>  	You should put your personal name, generally a form using a given name
>  	and family name.  For example, the current maintainer of Git uses "Junio
> -	C Hamano".  This will be the name portion that is stored in every commit
> +	C Hamano". This will be the name portion that is stored in every commit
>  	you make.
>  +
>  This configuration doesn't have any effect on authenticating to remote services;
> @@ -32,7 +32,7 @@ for that, see `credential.username` in linkgit:git-config[1].
>  [[http-postbuffer]]
>  What does `http.postBuffer` really do?::
>  	This option changes the size of the buffer that Git uses when pushing
> -	data to a remote over HTTP or HTTPS.  If the data is larger than this
> +	data to a remote over HTTP or HTTPS. If the data is larger than this
>  	size, libcurl, which handles the HTTP support for Git, will use chunked
>  	transfer encoding since it isn't known ahead of time what the size of
>  	the pushed data will be.
> @@ -40,15 +40,15 @@ What does `http.postBuffer` really do?::
>  Leaving this value at the default size is fine unless you know that either the
>  remote server or a proxy in the middle doesn't support HTTP/1.1 (which
>  introduced the chunked transfer encoding) or is known to be broken with chunked
> -data.  This is often (erroneously) suggested as a solution for generic push
> +data. This is often (erroneously) suggested as a solution for generic push
>  problems, but since almost every server and proxy supports at least HTTP/1.1,
> -raising this value usually doesn't solve most push problems.  A server or proxy
> +raising this value usually doesn't solve most push problems. A server or proxy

All of the above look useless noise.  It's not like it is turning
multiple SP after full-stop into a single SP (there is one that is
not touched in the pre-context in the first hunk, for example)---
not that such a change is worth a churn.

Please split them out and concentrate on true errors and typoes;
otherwise it is too distracting and unreviewable.

Thanks.