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

Re: nested git repos (not submodules)

From
Andrew Ardill <andrew.ardill@gmail.com>
Date
Feb 10, 2012, 03:47 UTC
Message-ID
<CAH5451mU5G-_FaPkpuhKrHAt4_5wiECj=-j9wkA_Ctb=27ncQg@mail.gmail.com>
In-Reply-To
<jh1vo3$7af$1@dough.gmane.org>
> Thanks in advance for any feedback.

My understanding was that such a configuration is essentially tracking the same set of files in two different git repositories. The location of the .git is not important, I could just as easily set the working directory of any git repository to be a folder tracked by another repository.

My concerns would be based primarily on the different repositories trying to act on the same files at the same time. Ignoring the sub-folder completely within the encompassing repository would avoid that, however you might have use cases that prohibit that.

Out of interest, what itch are you scratching by using this model?
Regards,
Andrew Ardill
Previous: Neal KreitzingerNext: Neal Kreitzinger
Message 2 of 5 in “nested git repos (not submodules)”
  1. Neal KreitzingerFeb 10, 2012
  2. Andrew ArdillFeb 10, 2012
  3. Neal KreitzingerFeb 10, 2012
  4. Junio C HamanoFeb 10, 2012
  5. Neal KreitzingerFeb 10, 2012

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.