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

[PATCH] gitworkflows: fix grammar in 'Merge upwards' rule

From
Kyle Meyer <kyle@kyleam.com>
Date
Jun 9, 2018, 15:19 UTC
Message-ID
<20180609151943.7387-1-kyle@kyleam.com>
Signed-off-by: Kyle Meyer <kyle@kyleam.com>
---
 Documentation/gitworkflows.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/gitworkflows.txt b/Documentation/gitworkflows.txt
index 926e044d0..ca11c7bda 100644
--- a/Documentation/gitworkflows.txt
+++ b/Documentation/gitworkflows.txt
@@ -107,7 +107,7 @@ the unstable branch into the stable one.  Hence the following:
 .Merge upwards
 [caption="Rule: "]
 =====================================
-Always commit your fixes to the oldest supported branch that require
+Always commit your fixes to the oldest supported branch that requires
 them.  Then (periodically) merge the integration branches upwards into each
 other.
 =====================================

-- 
2.11.0
Next: Elijah Newren
Message 1 of 2 in “gitworkflows: fix grammar in 'Merge upwards' rule”
  1. gitworkflows: fix grammar in 'Merge upwards' ruleKyle Meyer, Jun 9, 2018
  2. Elijah NewrenJun 9, 2018

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.