git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] added missing backtick in git-apply.txt

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 28, 2009, 21:10 UTC
Message-ID
<7vy6vqe09e.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1235851434-16950-1-git-send-email-dt@korn.shell.la>
dt@korn.shell.la writes:
Show 20 quoted lines
> From: Danijel Tasov <dt@korn.shell.la>
>
> Signed-off-by: Danijel Tasov <dt@korn.shell.la>
> ---
>  Documentation/git-apply.txt |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/git-apply.txt b/Documentation/git-apply.txt
> index 9400f6a..0566376 100644
> --- a/Documentation/git-apply.txt
> +++ b/Documentation/git-apply.txt
> @@ -159,7 +159,7 @@ on the command line, and ignored if there is any include pattern.
>  	considered whitespace errors.
>  +
>  By default, the command outputs warning messages but applies the patch.
> -When `git-apply is used for statistics and not applying a
> +When `git-apply` is used for statistics and not applying a
>  patch, it defaults to `nowarn`.
>  +
>  You can use different `<action>` to control this
Thanks.

This was caused by the large documentation churn 483bc4f (Documentation formatting and cleanup, 2008-06-30) that was supposed to be a clean-up. Can people lend eyeballs to see if there isn't any other such typo remaining? I briefly looked at the commit again and I think it is Ok now, but I obviously missed this when I first applied the patch, so...

Previous: dt@korn.shell.la
Message 2 of 2 in “added missing backtick in git-apply.txt”
  1. added missing backtick in git-apply.txtdt@korn.shell.la, Feb 28, 2009
  2. Junio C HamanoFeb 28, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.