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

Re: Sharing nested subparts of large repository?

From
LLordSmoke <dslice@morphometrics.org>
Date
Apr 5, 2012, 08:32 UTC
Message-ID
<1333614754844-7439149.post@n2.nabble.com>
In-Reply-To
<1332957138457-7414676.post@n2.nabble.com>

Okay, it seems submodules really were the answer. I split my app into a standalone public subtree and a development subtree that will use the public source as a submodule (haven't actually done that yet, though). These will be excluded from the parent git repository, but I guess that is fine since the parent is used mainly for archiving and the remote repository serves as the code archive.

-- View this message in context: http://git.661346.n2.nabble.com/Sharing-nested-subparts-of-large-repository-tp7403743p7439149.html Sent from the git mailing list archive at Nabble.com.

Previous: LordSmoke
Message 7 of 7 in “Sharing nested subparts of large repository?”
  1. LordSmokeMar 25, 2012
  2. Phil HordMar 26, 2012
  3. Dennis E. SliceMar 26, 2012
  4. Neal KreitzingerMar 28, 2012
  5. LordSmokeMar 28, 2012
  6. LordSmokeMar 29, 2012
  7. LordSmokeApr 5, 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.