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

Re: [PATCH v2] submodule: Allow tracking of the newest revision of a branch in a submodule

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 11, 2008, 19:26 UTC
Message-ID
<7voczicy2w.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1229001361-9301-1-git-send-email-git@fabian-franz.de>
Fabian Franz <git@fabian-franz.de> writes:
Show 11 quoted lines
> So my workflow really is:
>
> git checkout master # done long before
> [...]
> git checkout staging
> # => in submodules/client/
> # Checked out submodules/client/ staging.
> # => in submodules/client/component1/
> # Checked out submodules/client/component/1 staging.
>
> So I would like to have this recursively...
Didn't we add foreach subcommand to the submodule command?
Previous: Johannes Sixt
Message 3 of 3 in “submodule: Allow tracking of the newest revision of a branch in a submodule”
  1. submodule: Allow tracking of the newest revision of a branch in a submoduleFabian Franz, Dec 11, 2008
  2. Johannes SixtDec 11, 2008
  3. Junio C HamanoDec 11, 2008

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.