> What I was "handwaving" (or "envisioning") was to have something > like this in .gitmodules: > > [subproject "kernel/"] > URL = git://git.kernel.org/pub/linux-2.4.git > > (or 2.6, depending on the revision of the superproject) and per > repository configuration would maps this with these two entries: > > [subproject "git://git.kernel.org/pub/linux-2.4.git"] > URL = http://www.kernel.org/pub/linux-2.4.git > > [subproject "git://git.kernel.org/pub/linux-2.6.git"] > URL = http://www.kernel.org/pub/linux-2.6.git > > The intent is > > (1) "kernel/" directory is found to be a gitlink in the > tree/index; .gitmodules is consulted to find the > "URL", which is just a handle and the initial hint > > (2) That "initial hint" is used to look up the > subproject entry from the configuration, to find the > "real" URL that is used by this repository I'm reading up on submodules, two questions on this: 1. I understand the usefulness of the hint for public repositories, (the user might need help discovering where to get submodules) but for private ones would this create a hassle: I start with a subproject in ~/subprojecttest and if that gets put in the URL hint, I have to maintain a map for ~/subprojecttest in my .git/config forever even after I move it to ~/subprojectproduction, just to make old releases build? Do you think it might make sense to support a mode where .gitmodules is empty, and URLs come from the config directly? 2. Suppose .gitmodules in upstream tree points at subproject repo at kernel.org, and I clone from there - my repo will point at kernel.org by default? But now, I'd like everyone who clones from *my* repo to get pointed at *my* server by default (e.g. for mirroring), but would not changing .gitmodules create a commit so my head will now differ from upstream - so it won't be signed properly etc... Did I misunderstand something? -- MST - 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
