Re: [PATCH] Documentation: use "command-line" when used as a compound adjective, and fix other minor grammatical issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Jason St. John" <jstjohn@xxxxxxxxxx> writes:

> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
> index 022e74e..01200ed 100644
> --- a/Documentation/user-manual.txt
> +++ b/Documentation/user-manual.txt
> @@ -173,13 +173,13 @@ index 65898fa..b002dc6 100644
>  --- a/init-db.c
>  +++ b/init-db.c
>  @@ -7,7 +7,7 @@
> - 
> +
>   int main(int argc, char **argv)
>   {
>  -	char *sha1_dir = getenv(DB_ENVIRONMENT), *path;
>  +	char *sha1_dir, *path;
>   	int len, i;
> - 
> +
>   	if (mkdir(".git", 0755) < 0) {
>  ------------------------------------------------

I know it would not make any difference either way when printed, but
aren't we showing how a typical diff output looks like with this
example, and each of these two otherwise blank lines should actually
be a line with a single SP on it?

Everything else looked fine.  Thanks for cleaning the docs up.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]