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

[PATCH] fix typo 'In such these cases'

From
RNRené Nyffenegger <mail@renenyffenegger.ch>
Date
May 2, 2016, 07:38 UTC
Message-ID
<572703EC.20405@renenyffenegger.ch>
From 5e2b47833c8d434784fa1a797cfd6a087df10dc8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ren=C3=A9=20Nyffenegger?= <rene.nyffenegger@adp-gmbh.ch>
Date: Mon, 2 May 2016 09:19:46 +0200
Subject: [PATCH] Documentation: Fix typo 'In such these cases'

Fix "In such these cases, ..." to "In such cases, ..." in Documentation/glossary-content.txt

Signed-off-by: René Nyffenegger <mail@renenyffenegger.ch>
---
 Documentation/glossary-content.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
index cafc284..9ceca05 100644
--- a/Documentation/glossary-content.txt
+++ b/Documentation/glossary-content.txt
@@ -145,7 +145,7 @@ current branch integrates with) obviously do not work, as there is no
 	A fast-forward is a special type of <<def_merge,merge>> where you have a
 	<<def_revision,revision>> and you are "merging" another
 	<<def_branch,branch>>'s changes that happen to be a descendant of what
-	you have. In such these cases, you do not make a new <<def_merge,merge>>
+	you have. In these cases, you do not make a new <<def_merge,merge>>
 	<<def_commit,commit>> but instead just update to his
 	revision. This will happen frequently on a
 	<<def_remote_tracking_branch,remote-tracking branch>> of a remote
-- 
2.5.0
Next: Junio C Hamano
Message 1 of 5 in “fix typo 'In such these cases'”
  1. fix typo 'In such these cases'René Nyffenegger, May 2, 2016
  2. Junio C HamanoMay 2, 2016
  3. René NyffeneggerMay 2, 2016
  4. Junio C HamanoMay 2, 2016
  5. René NyffeneggerMay 2, 2016

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.