Re: [PATCH v2 2/4] Doc: add more detail for git-format-patch
From: Eric Sunshine <hidden>
Date: 2019-08-20 02:44:17
On Mon, Aug 19, 2019 at 7:53 PM Denton Liu [off-list ref] wrote:
In git-format-patch.txt, we were missing some key user information. First of all, using the `--to` and `--cc` options don't override `format.to` and `format.cc` variables, respectively. They add on to each other. Document this.
This entire paragraph can go away since v2 dropped this change.
quoted hunk ↗ jump to hunk
In addition, document the special value of `--base=auto`. Next, while we're at it, surround option arguments with <>. Finally, document the `format.outputDirectory` config and change `format.coverletter` to use camel case. Signed-off-by: Denton Liu <redacted> ---diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt@@ -314,7 +314,8 @@ you can use `--suffix=-patch` to get `0001-description-of-my-change-patch`. --base=<commit>:: Record the base tree information to identify the state the patch series applies to. See the BASE TREE INFORMATION section - below for details. + below for details. If <commit> is "auto", a base commit is + automatically chosen.
Should <commit> be encased in backquotes in the paragraph body?