Re: [PATCH v2 2/5] doc: git-diff: apply format changes to diff-options

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

 



"Jean-Noël Avila via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes:

> --s::
> ---no-patch::
> +`-s`::
> +`--no-patch`::

These are understandable.  These dashed options that are to be given
literally are shown as `literal`.

> @@ -39,28 +39,28 @@ endif::git-format-patch[]
>  ifdef::git-log[]
>  -m::

Shouldn't this and all others like -c/--cc be also quoted as
`literal` options?

> @@ -73,33 +73,33 @@ The following formats are supported:
>  off, none::

Shouldn't this and other option values like on, first-parent, etc.,
that are literals be marked-up specially?

> --U<n>::
> ---unified=<n>::
> -	Generate diffs with <n> lines of context instead of
> +`-U<n>`::
> +`--unified=<n>`::
> +	Generate diffs with _<n>_ lines of context instead of

Understandable.  Shouldn't <n> part be italicised?

> ---output=<file>::
> +`--output=<file>`::

Likewise.

Thanks.




[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]

  Powered by Linux