Taylor BlauIn [1] Git learned about 'core.alternateRefsCommand', and with it, the accompanying documentation. However, this documentation included a typo involving the verb tense of "produced".
Match the tense of the surrounding bits by correcting this typo.
[1]: 89284c1d6c (transport.c: introduce core.alternateRefsCommand,
2018-10-08)Signed-off-by: Taylor Blau <me@ttaylorr.com> ---
Note: this can be applied as a fixup to the commit [1] mentioned above. I'm sending it as a separate series, since the patches have already landed on 'next'.
They were originally introduced in:
7451b4872a0fd66d84cbe492fdfe7a9a8e81eab7.1539021825.git.me@ttaylorr.com
I think that these will ultimately conflict with Duy's patches to move Documentation/config.txt out to separate files. It seems, however, that he may re-roll the series beforehand, so I can either:
1. Resend this once he has landed his changes, or,
2. He can re-roll with this version of Documentation/config.txt.
Documentation/config.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Show changes to Documentation/config.txt +1 −2
diff --git a/Documentation/config.txt b/Documentation/config.txt index 552827935a..09e95e9e98 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -620,7 +620,7 @@ core.alternateRefsCommand:: When advertising tips of available history from an alternate, use the shell to execute the specified command instead of linkgit:git-for-each-ref[1]. The first argument is the absolute path of the alternate. Output must contain one - hex object id per line (i.e., the same as produce by `git for-each-ref + hex object id per line (i.e., the same as produced by `git for-each-ref --format='%(objectname)'`). + Note that you cannot generally put `git for-each-ref` directly into the config -- 2.19.0.221.g150f307af