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

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

From
Elijah Newren <newren@gmail.com>
Date
Jun 9, 2018, 20:14 UTC
Message-ID
<CABPp-BG_4WRP=-m7RfqAdYvOrM5CnByHZ=yghPqTdOcL2NGjhQ@mail.gmail.com>
In-Reply-To
<20180609151943.7387-1-kyle@kyleam.com>
Hi Kyle,
On Sat, Jun 9, 2018 at 8:19 AM, Kyle Meyer <kyle@kyleam.com> wrote:
Show 18 quoted lines
> 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.
>  =====================================
Thanks for sending in the fix.
Reviewed-by: Elijah Newren <newren@gmail.com>
Previous: Kyle Meyer
Message 2 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.