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

Re: [PATCH/RFC v2] Squashed changes for multiple worktrees vs. submodules

From
Duy Nguyen <pclouds@gmail.com>
Date
Dec 1, 2014, 10:43 UTC
Message-ID
<CACsJy8C1968-NJAxvxnwXAOZTofedpAe+Rmg4OYJA4E3t9Ao+g@mail.gmail.com>
In-Reply-To
<1417390076-2953-1-git-send-email-max@max630.net>
On Mon, Dec 1, 2014 at 6:27 AM, Max Kirillov <max@max630.net> wrote:
Show 8 quoted lines
> But, while hacking the submodule init I became more convinced that the
> modules directory should be common and submodules in checkout should be
> a checkouts of the submodule. Because this is looks like concept of
> submodules, that they are unique for the lifetime of repository, even if
> they do not exist in all revisions. And if anybody want to use fully
> independent checkout they can be always checked out manually. Actually,
> after a submodule is initialized and have a proper gitlink, it can be
> updated and inquired regardless of where it points to.

Just throw something in for discussion. What about keeping $GIT_DIR/modules like it is now (i.e. not shared) and add $GIT_DIR/shared-modules, which is the same for all checkouts? That would keep current submodule code happy (no name collision or anything). New submodule code can start using $GIT_DIR/shared-modules while still keeping an eye on $GIT_DIR/modules for old setups.

-- 
Duy
Previous: Max KirillovNext: Max Kirillov
Message 2 of 14 in “Squashed changes for multiple worktrees vs. submodules”
  1. Squashed changes for multiple worktrees vs. submodulesMax Kirillov, Nov 30, 2014
  2. Duy NguyenDec 1, 2014
  3. Max KirillovDec 1, 2014
  4. Jens LehmannDec 2, 2014
  5. Max KirillovDec 2, 2014
  6. Jens LehmannDec 4, 2014
  7. Duy NguyenDec 5, 2014
  8. Jens LehmannDec 6, 2014
  9. Max KirillovDec 5, 2014
  10. Jens LehmannDec 6, 2014
  11. Max KirillovDec 7, 2014
  12. Max KirillovDec 7, 2014
  13. Jens LehmannDec 8, 2014
  14. Max KirillovDec 8, 2014

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.