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

Re: [PATCH 1/1] Fix typo in merge-strategies documentation

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 19, 2018, 16:51 UTC
Message-ID
<xmqqo9jkvwjh.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20180317033142.20119-2-david.pursehouse@gmail.com>
David Pursehouse <david.pursehouse@gmail.com> writes:
> From: David Pursehouse <dpursehouse@collab.net>
>
> Signed-off-by: David Pursehouse <dpursehouse@collab.net>
> ---

I somehow had to stare at the patch for a few minutes, view it in two Emacs buffers and run M-x compare-windows before I finally spot the single-byte typofix.

Will queue with a retitle.
    Documentation/merge-strategies: typofix
    
    It's strategy, not stragegy.
    
    Signed-off-by: David Pursehouse <dpursehouse@collab.net>
    Signed-off-by: Junio C Hamano <gitster@pobox.com>
Thanks.
Show 16 quoted lines
>  Documentation/merge-strategies.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/merge-strategies.txt b/Documentation/merge-strategies.txt
> index fd5d748d1..4a58aad4b 100644
> --- a/Documentation/merge-strategies.txt
> +++ b/Documentation/merge-strategies.txt
> @@ -40,7 +40,7 @@ the other tree did, declaring 'our' history contains all that happened in it.
>  
>  theirs;;
>  	This is the opposite of 'ours'; note that, unlike 'ours', there is
> -	no 'theirs' merge stragegy to confuse this merge option with.
> +	no 'theirs' merge strategy to confuse this merge option with.
>  
>  patience;;
>  	With this option, 'merge-recursive' spends a little extra time
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 4 of 7 in “Fix typo in merge-strategies documentation”
  1. 0/1 Fix typo in merge-strategies documentationDavid Pursehouse, Mar 17, 2018
  2. 1/1 Fix typo in merge-strategies documentationDavid Pursehouse, Mar 17, 2018
  3. Johannes SchindelinMar 19, 2018
  4. Junio C HamanoMar 19, 2018
  5. Johannes SchindelinMar 21, 2018
  6. Junio C HamanoMar 22, 2018
  7. David PursehouseMar 21, 2018

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.