On Mon, Jul 28, 2008 at 08:23:39PM +0000, Nigel Magnay wrote: > > > > While trying to sum up some things I'd like submodules to do, and things > > like that, I came to ask myself why the heck we were doing things the > > way we currently do wrt submodules. > > > > This question is related to the `.git` directories of submodules. I > > wonder why we didn't chose to use a new reference namespace > > (refs/submodules/$path/$remote/$branch). > > > I'm maybe being a bit slow - what would be the contents of (say) > refs/submodules/moduleA/remotes/origin/master ? The ref > that's currently in moduleA/.git/refs/remotes/origin/master ? Yes. > > It also has the absolutely nice property to share objects, so that > > projects that replaced a subdirectory with a submodule don't see their > > checkouts grow too large. > > > > Ah.. are you meaning that the top-level repository contains all the > commits in all the submodules? Yes. My suggestion is to share all the references, prefixing the submodules ones with a distinct prefix (namely refs/submodules/$name-of-the-submodule) to avoid any conflict, and share the object store. You get coherent reflogs and stuff like that for free on top. > I was thinking a bit about submodules (because of the earlier > discussions about submodule update only pulling from origin, and the > associated difficulties) and started wondering if the best place for > the git repository for (say) submoduleA was really > <...>/submoduleA/.git/<> and not (say) something like > ..git/submodules/submoduleA/<>. This would be nicer for people trying > to pull revisions from you because they could easily find submodule > repositories regardless or not of whether they currently exist in your > WC. That too indeed (the "easier to clone" bit). OTOH, I don't like the .git/submodules idea a lot, if you mean to put a usual $GIT_DIR layout inside of it. With what I propose, you find objects for all your super/sub-modules in the usual store, which eases many things. Especially, I believe that when you replace a subdirectory of a project with a submodule, git-blame could benefit quite a lot from this to be able to glue history back through the submodule limits, without having to refactor a _lot_ of code: it would merely have to dereference so called "gitlinks" to the commit then tree, hence twice, and just do its usual work, with your proposal, we still rely on having to recurse in subdirectories which requires more boilerplate code. > I got as far as looking at discussions around .gitlink but ran out of > avaiable time. I shall say I never followed them, as I was uninterested with such subjects before, (but now is as I use them at work). But I don't recall such an idea to have been discussed at all, so... > > Having that, one can probably extend most of the porcelains in _very_ > > straightforward ways. For example, a local topic branch `topic` would be > > the union of the supermodule `topic` branch, and all the > > `refs/submodules/$names/topic` ones. > > > > Most importantly, it would help implementing that tries to make your > > submodules stay _on branch_. One irritating problem with submodules, is > > that when someone else commited, and that you git submodule update, > > you're on a detached head. Absolutely horrible. If you see your current > > branch (assume it's master), then when you do that, you would update > > your `refs/submodules/$name/master` references instead and keep the > > submodule HEADs `on branch`. Of course we can _probably_ hack something > > together along those lines with the current setup, but it would be _so_ > > much more convenient this way... > > > > For me, if I'm on heads/blah in the superproject, I probably want to > be on heads/blah in *all* submodules. But that's maybe just me. Yes, that's what I tried to say, so if it wasn't clear, it's exactly what I would like to do/have. -- ·O· Pierre Habouzit ··O madcoder@xxxxxxxxxx OOO http://www.madism.org
Attachment:
pgpemW4bKMo2s.pgp
Description: PGP signature
