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

Re: Nesting a submodule inside of another...

From
Jens Lehmann <jens.lehmann@web.de>
Date
Jul 13, 2011, 22:04 UTC
Message-ID
<4E1E1672.7040503@web.de>
In-Reply-To
<7vhb6p6fcl.fsf@alter.siamese.dyndns.org>
Am 13.07.2011 23:27, schrieb Junio C Hamano:
Show 5 quoted lines
> Jens Lehmann <Jens.Lehmann@web.de> writes:
> 
>> It can't be communicated, as submodules are unaware of their superproject.
> 
> It's more like s/can't/shouldn't/ and s/are/shouldn't be/, no?

Right. Submodules /could/ be taught to check if they are part of a superproject, but unless I miss something obvious they are currently totally unaware of that (at least when it concerns their work tree, the gitfile effort is trying to introduce some superproject awareness). And as far as I can see that is a sound design decision as far as it concerns the work tree. Imagine the files and/or directories a submodule has to ignore would depend on the settings of their superproject too (which is what this thread is about). That would lead to very interesting problems when the same submodule would be used by different superprojects which ignore different files and/or directories inside the submodule, which - to make things even more interesting - might be recorded in the submodule itself ... not good.

So what about: s/can't/isn't and shouldn't/ and s/are/are and shouldn't/?
Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 11 in “Nesting a submodule inside of another...”
  1. John SzakmeisterJul 12, 2011
  2. Jens LehmannJul 12, 2011
  3. John SzakmeisterJul 13, 2011
  4. Jens LehmannJul 13, 2011
  5. Junio C HamanoJul 13, 2011
  6. Jens LehmannJul 13, 2011
  7. Junio C HamanoJul 13, 2011
  8. John SzakmeisterJul 14, 2011
  9. Seth RobertsonJul 14, 2011
  10. John SzakmeisterJul 15, 2011
  11. Andreas EricssonJul 13, 2011

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.