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

[PATCH] docs: fix grammar in gitattributes.txt

From
Alexei Sholik <alcosholik@gmail.com>
Date
Mar 18, 2011, 13:14 UTC
Message-ID
<1300454067-9934-1-git-send-email-alcosholik@gmail.com>
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.
 
 String::
-- 
1.7.2.3
Next: Marc Branchaud
Message 1 of 3 in “docs: fix grammar in gitattributes.txt”
  1. docs: fix grammar in gitattributes.txtAlexei Sholik, Mar 18, 2011
  2. Marc BranchaudMar 18, 2011
  3. Junio C HamanoMar 18, 2011

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.