On Fri, Jul 22, 2016 at 10:42 AM, Duy Nguyen <pclouds@xxxxxxxxx> wrote: > On Fri, Jul 22, 2016 at 7:25 PM, Stefan Beller <sbeller@xxxxxxxxxx> wrote: >> On Fri, Jul 22, 2016 at 10:09 AM, Duy Nguyen <pclouds@xxxxxxxxx> wrote: >>> >>> I just quickly glanced through the rest of this mail because, as a >>> submodule ignorant, it's just mumbo jumbo to me. But what I see here >>> is, there may be problems if we choose to share some submodule info, >>> but I haven't seen any good thing from sharing any submodule info at >>> all. >> >> Okay. :( > > Didn't mean to make you feel sad :) I was using the :( a bit carelessly here. I was quite surprised that you "haven't seen any good thing from sharing any submodule info at all." So what is the design philosophy in worktrees? How much independence does one working tree have? So here is what I did: * s/git submodule init/git submodule update --init/ * added a test_pause to the last test on the last line * Then: $ find . |grep da5e6058 ./addtest/.git/modules/submod/objects/08/da5e6058267d6be703ae058d173ce38ed53066 ./addtest/.git/worktrees/super-elsewhere/modules/submod/objects/08/da5e6058267d6be703ae058d173ce38ed53066 ./addtest/.git/worktrees/super-elsewhere/modules/submod2/objects/08/da5e6058267d6be703ae058d173ce38ed53066 ./.git/objects/08/da5e6058267d6be703ae058d173ce38ed53066 The last entry is the "upstream" for the addtest clone, so that is fine. However inside the ./addtest/ (and its worktrees, which currently are embedded in there?) we only want to have one object store for a given submodule? > >> I assume the sharing is beneficial. (As a work-tree ignorant) I thought >> we had this main work tree, which also holds the repository, whereas >> the other working trees have a light weight implementation (e.g. just >> a .git file pointing back to the main working tree/git dir). > > The main worktree is special for historical reason. But from the user > point of view (and even developer's at a certain level) they should be > treated equally. Think of it like cloning the same repo multiple > times. Only now you save disk space because there's only one object > database. That's what we want for submodules too, see above? > >> So in a way my mental model is more like the config sharing here >> You can configure things in ~/.gitconfig for example that have effects >> on more than one repo. Similarly you would want to configure things >> in one repo, that has effect on more than one working tree? >> >> And my assumption was to have the repository specific parts be shared, >> whereas the working tree specific things should not be shared. > > I think that's a good assumption. Although I would rather be not > sharing by default and let the user initiate it when they want to > share something. Like ~/..gitconfig, we never write anything there > unless the user asks us to explicitly (with git config --user). > Accidental share could have negative effect. Okay, got it. > >>> I can imagine long term you may want to just clone a submodule repo >>> once and share it across worktrees that use it, so maybe it's just me >>> not seeing things and this may be a step towards that. >> >> Just as Junio put it: >>> I agree that when a top-level superproject has multiple worktrees >>> these multiple worktrees may want to have the same submodule in >>> different states, but I'd imagine that they want to share the same >>> physical repository (i.e. $GIT_DIR/modules/$name of the primary >>> worktree of the superproject)---is everybody involved in the >>> discussion share this assumption? >> >> I agree with that as well. > > Yeah. We have a long way to go though. As I see it, you may need ref > namespace as well (so they look like separate clones), which has never > been used on the client side before. Either that or odb alternates... > >>> And because I have not heard any bad thing about the new config >>> design, I'm going to drop submodule patches from this series and focus >>> on polishing config stuff. >> >> Oh, sorry for not focusing on that part. The design of git config --worktree >> is sound IMO. > > This makes me happy (I know other people can still find flaws in it, > and I'm ok with that). This config split thing has been wrecking my > brain for a long time, find the the "right" way to do with minimum > impacts :) After playing with this series a bit more, I actually like the UI as it is an easy mental model "submodules behave completely independent". However in 3/4 you said: + - `submodule.*` in current state should not be shared because the + information is tied to a particular version of .gitmodules in a + working directory. This is already a problem with say different branches/versions. That has been solved by duplicating that information to .git/config as a required step. (I don't like that approach, as it is super confusing IMHO) + + - `remote.*` added by submodules may be per working directory as + well, unless you are sure remotes from all possible submodules in + history are consistent. + Same as above. I planned to have a series out last Friday, but it took longer than expected as it was unclear how to best proceed and I ran into problems solving "trivial issues". I am back to the drawing board for the submodule side of things, but I guess this series could be used once we figure out how to have just one object database for a submodule. Thanks, Stefan > -- > Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html