From: Duy Nguyen <pclouds@gmail.com>
Date: Mon, 01 Dec 2014 10:43:16 GMT
Subject: Re: [PATCH/RFC v2] Squashed changes for multiple worktrees vs. submodules
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:
> 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