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

Re: How to work with submodule?

From
Steffen Prohaska <prohaska@zib.de>
Date
Aug 10, 2007, 07:29 UTC
Message-ID
<3E1A1FB8-AD4D-4733-8525-4DAECD754F65@zib.de>
In-Reply-To
<769ABF7E-14C9-43D1-B879-138B6FF96B2E@zib.de>
On Aug 10, 2007, at 9:02 AM, Steffen Prohaska wrote:
> I mean, I should be allowed to work on the submodule and somehow
> work on the superproject at the same time? But none of my
> usual workflow works because I always get trapped by a
> modified submodule.

What I do now is to check with 'git diff' in the supermodule, which state of the submodule is expected. Then I bring the submodule in this state (even if this brings me to a detached head). This keeps the supermodule happy.

But if different branches of the supermodule expect different states of the submodule you may be forced to switch to another detached head after every command you run in the supermodule. There must be a simpler way, which I probably don't know.

	Steffen
Previous: Steffen Prohaska
Message 2 of 2 in “How to work with submodule?”
  1. Steffen ProhaskaAug 10, 2007
  2. Steffen ProhaskaAug 10, 2007

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.