Re: [PATCH v5 00/28] Support multiple checkouts

From: Duy Nguyen <pclouds@gmail.com>
Date: Jul 7, 2014, 10:25 UTC
Message-ID: <CACsJy8D=9vVkZ2PtZq=b6R6wEmr1pX-yxCCXVBrd-akfeqE1sQ@mail.gmail.com>
In-Reply-To: <20140706204651.GB21237@wheezy.local>

On Mon, Jul 7, 2014 at 3:46 AM, Max Kirillov <max@max630.net> wrote:

Show 7 quoted lines

> Hi.
>
> What future does this have? Currently it is marked as
> "Stalled", but still mergeable with some trivial conflicts
> and seem to be working (except some bugs in interaction with
> submodules, see below). It would be very nice if this
> feature is officially supported.

It's to be re-rolled soon. I have a patch about sparse-checkout and Dennis may contribute another one to enable "checkout --to" from a bare repository. By the way Dennis has been testing this feature and he reported (off-list) it worked fine, which is good news. I have done nothing so far because my git time (or energy to be precise) is limited these days, and I wanted to see if Dennis reported any new bugs.

Show 6 quoted lines

> I also have a comment about how it interacts with submodules.
> Would it be more appropriate to mark "modules" as a
> per-checkout directory? Because each of the working tree's
> submodule is obviously a separated directory in filesystem,
> and in most cases (at least in my practice) they are
> checked-out to different revisions.

Submodule interaction is something I have avoided so far because I'm not a big user and admittedly does not follow its development closely. I think we could get this in first, then let submodule people aware about this feature and let them decide how to use it.

Show 11 quoted lines

> So, currently (before proper linking of submodules checkouts
> implemented), if make submodules per-checkout (actually it
> appears to somehow work even with current code, maybe
> because some submodule code ignores the common_dir), one
> could run "git submodule update" if necessary, and get fully
> separated clones, which would work normally.
>
> It still may break if submodules are removed, added or
> renamed, but this seems to be inevitable until config is
> separated to per-checkout and common parts, which I suppose
> is a much bigger task.

-- 
Duy