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

[PATCH 1/4] docs/merge-strategies: remove hyphen from mis-merges

From
AIAlbert L. Lash, IV <albert.lash@gmail.com>
Date
Feb 8, 2014, 20:41 UTC
Message-ID
<1391892097-16169-1-git-send-email-alash3@bloomberg.net>

The term mismerges without hyphen is used a few other places in the documentation. Let's update this to be consistent.

Signed-off-by: Albert L. Lash, IV <alash3@bloomberg.net>
---
 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 fb6e593..3509498 100644
--- a/Documentation/merge-strategies.txt
+++ b/Documentation/merge-strategies.txt
@@ -20,7 +20,7 @@ recursive::
 	merged tree of the common ancestors and uses that as
 	the reference tree for the 3-way merge.  This has been
 	reported to result in fewer merge conflicts without
-	causing mis-merges by tests done on actual merge commits
+	causing mismerges by tests done on actual merge commits
 	taken from Linux 2.6 kernel development history.
 	Additionally this can detect and handle merges involving
 	renames.  This is the default merge strategy when
-- 
1.8.3.2
Next: Albert L. Lash, IV
Message 1 of 7 in “docs/merge-strategies: remove hyphen from mis-merges”
  1. 1/4 docs/merge-strategies: remove hyphen from mis-mergesAlbert L. Lash, IV, Feb 8, 2014
  2. 2/4 docs/git-remote: capitalize first word of initial blurbAlbert L. Lash, IV, Feb 8, 2014
  3. 3/4 docs/git-clone: clarify use of --no-hardlinks optionAlbert L. Lash, IV, Feb 8, 2014
  4. Junio C HamanoFeb 11, 2014
  5. 4/4 docs/git-blame: explain more clearly the example pickaxe useAlbert L. Lash, IV, Feb 8, 2014
  6. Junio C HamanoFeb 11, 2014
  7. Junio C HamanoFeb 10, 2014

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.