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

Re: [PATCH] Grammar fixes to "merge" and "patch-id" docs

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 25, 2009, 18:33 UTC
Message-ID
<7vocvp310v.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1238005422-7647-1-git-send-email-win@wincent.com>
Wincent Colaiuta <win@wincent.com> writes:
>  If you tried a merge which resulted in a complex conflicts and
> -would want to start over, you can recover with 'git-reset'.
> +want to start over, you can recover with 'git-reset'.
Reads Ok to me either way...
Show 11 quoted lines
> diff --git a/Documentation/merge-strategies.txt b/Documentation/merge-strategies.txt
> index 1276f85..ee7f754 100644
> --- a/Documentation/merge-strategies.txt
> +++ b/Documentation/merge-strategies.txt
> @@ -3,15 +3,15 @@ MERGE STRATEGIES
>  
>  resolve::
>  	This can only resolve two heads (i.e. the current branch
> -	and another branch you pulled from) using 3-way merge
> +	and another branch you pulled from) using a 3-way merge
>  	algorithm.  It tries to carefully detect criss-cross
Hmph, would that be an 'a' or 'the'?
Show 7 quoted lines
>  recursive::
> -	This can only resolve two heads using 3-way merge
> -	algorithm.  When there are more than one common
> -	ancestors that can be used for 3-way merge, it creates a
> +	This can only resolve two heads using a 3-way merge
> +	algorithm.  When there is more than one common
> +	ancestor that can be used for 3-way merge, it creates a
Do you need an article before the latter "3-way merge", perhaps "the"?
Show 8 quoted lines
> @@ -22,11 +22,11 @@ recursive::
>  	pulling or merging one branch.
>  
>  octopus::
> -	This resolves more than two-head case, but refuses to do
> -	complex merge that needs manual resolution.  It is
> +	This resolves the more than two-heads case, but refuses to do
> +	a complex merge that needs manual resolution.  It is
Perhaps "resolves cases with more than two heads" is easier to read?
Previous: Wincent ColaiutaNext: Wincent Colaiuta
Message 2 of 5 in “Grammar fixes to "merge" and "patch-id" docs”
  1. Grammar fixes to "merge" and "patch-id" docsWincent Colaiuta, Mar 25, 2009
  2. Junio C HamanoMar 25, 2009
  3. Wincent ColaiutaMar 25, 2009
  4. Jeff KingMar 26, 2009
  5. Grammar fix for "git merge" man pageWincent Colaiuta, Mar 26, 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.