Re: [PATCH 14/14] builtin/checkout: add --recurse-submodules switch

From: Stefan Beller <sbeller@google.com>
Date: Feb 16, 2017, 00:33 UTC
Message-ID: <CAGZ79kbT2Gh70_OsE7d63pCxNSDb-RJBZmXsPKvkuRD9x__b9A@mail.gmail.com>
In-Reply-To: <20170215020851.awwddgprd7nsdbuv@genre.crustytoothpaste.net>

On Tue, Feb 14, 2017 at 6:08 PM, brian m. carlson <sandals@crustytoothpaste.net> wrote:

Show 9 quoted lines

> On Tue, Feb 14, 2017 at 04:34:23PM -0800, Stefan Beller wrote:
>> +--[no-]recurse-submodules::
>> +     Using --recurse-submodules will update the content of all initialized
>> +     submodules according to the commit recorded in the superproject. If
>> +     local modifications in a submodule would be overwritten the checkout
>> +     will fail until `-f` is used. If nothing (or --no-recurse-submodules)
>
> I would say "unless" instead of "until".  "Until" implies an ongoing
> or repetitive action being interrupted, which isn't the case here.

eh, of course.

$ 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.