From: Marc Branchaud <marcnarc@xiplink.com>
To: Alexei Sholik <alcosholik@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] docs: fix grammar in gitattributes.txt
Date: Fri, 18 Mar 2011 10:40:37 -0400 [thread overview]
Message-ID: <4D836EE5.7060003@xiplink.com> (raw)
In-Reply-To: <1300454067-9934-1-git-send-email-alcosholik@gmail.com>
On 11-03-18 09:14 AM, Alexei Sholik wrote:
> Signed-off-by: Alexei Sholik <alcosholik@gmail.com>
> ---
> Documentation/gitattributes.txt | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt
> index 7e7e121..c151657 100644
> --- a/Documentation/gitattributes.txt
> +++ b/Documentation/gitattributes.txt
> @@ -632,7 +632,7 @@ Performing a three-way merge
> `merge`
> ^^^^^^^
>
> -The attribute `merge` affects how three versions of a file is
> +The attribute `merge` affects how three versions of a file are
> merged when a file-level merge is necessary during `git merge`,
> and other commands such as `git revert` and `git cherry-pick`.
>
> @@ -646,15 +646,15 @@ Unset::
>
> Take the version from the current branch as the
> tentative merge result, and declare that the merge has
> - conflicts. This is suitable for binary files that does
> + conflicts. This is suitable for binary files that do
> not have a well-defined merge semantics.
>
> Unspecified::
>
> By default, this uses the same built-in 3-way merge
> - driver as is the case the `merge` attribute is set.
> + driver as is the case when the `merge` attribute is set.
> However, `merge.default` configuration variable can name
> - different merge driver to be used for paths to which the
> + different merge driver to be used with paths for which the
> `merge` attribute is unspecified.
That last sentence should really start like this:
- However, `merge.default` configuration variable can name
+ However, the `merge.default` configuration variable can name a
M.
next prev parent reply other threads:[~2011-03-18 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 13:14 [PATCH] docs: fix grammar in gitattributes.txt Alexei Sholik
2011-03-18 14:40 ` Marc Branchaud [this message]
2011-03-18 16:59 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D836EE5.7060003@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=alcosholik@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).