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

Re: [PATCH] document submodule sync --recursive

From
Stefan Beller <sbeller@google.com>
Date
Dec 3, 2015, 20:22 UTC
Message-ID
<CAGZ79kaX4ZM++jhPcpU0T8eYDobME=iNtbH3KceWbQOOavpHnA@mail.gmail.com>
In-Reply-To
<xmqqh9jzthh3.fsf@gitster.mtv.corp.google.com>
On Thu, Dec 3, 2015 at 12:17 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 6 quoted lines
>>
>> Tested-by: Per Cederqvist <cederp@opera.com>
>
> Isn't this Reported-by? (genuine question; I haven't caught up with
> my inbox backlog and do not claim having seen everything Per wrote
> to this list).

Per wrote he tested `git submodule sync --recursive` with 2.6.3, so yeah the tested refers to the underlying command, not this patch. So Reported-by is better here.

Show 8 quoted lines
>
>> Signed-off-by: Stefan Beller <sbeller@google.com>
>> ---
>>
>>  This applies on origin/master.
>
> Thanks.  Should it go to maintenance track (iow, was the feature
> that wasn't documented already in maint)?

It was introduced via (82f49f294c, Teach --recursive to submodule sync, 2012-10-26) so I guess maint is fine, too

Show 7 quoted lines
>> @@ -237,6 +237,9 @@ sync::
>>  +
>>  "git submodule sync" synchronizes all submodules while
>>  "git submodule sync \-- A" synchronizes submodule "A" only.
>> ++
>> +If `--recursive` is specified, this command will recurse into the
>> +registered submodules, and update any nested submodules within.
I should have paid more attention here and s/update/sync/.
I'll prepare a resend.
Previous: Junio C HamanoNext: Stefan Beller
Message 3 of 5 in “document submodule sync --recursive”
  1. document submodule sync --recursiveStefan Beller, Dec 3, 2015
  2. Junio C HamanoDec 3, 2015
  3. Stefan BellerDec 3, 2015
  4. [PATCHv2] document submodule sync --recursiveStefan Beller, Dec 3, 2015
  5. Junio C HamanoDec 4, 2015

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.