Avery Pennarun wrote: >> Well, that would create a lot of unnecessary work when cloning. >> Partitioning by project is a natural way to divide the projects up. > > What unnecessary work do you mean? A full clone takes a few shortcuts, especially over dumb transports like HTTP. I think there might be shortcuts in the git-daemon code as well. Forcing these to be partial might make these full fetches involve more time. >> However, what you are suggesting should IMHO be allowed to work. In >> particular, if the submodule path is ".", then I think there's a good >> case that they should come from within the same project. If it's a >> relative URL, it should initialize based on the remote URL that was used >> for the original fetch (or, rather, the remote URL for the current branch). > I agree, there's no reason to take away the existing functionality of > allowing split repos. I was more suggesting a new functionality so > that splitting isn't *required*. Yes - I look forward to a patch. >> This push failure thing is regrettable; however it's not clear which >> branch name the submodules should get. A given commit might exist on >> several branches, which one do you choose to name it? > One option is to make a simple "git push origin" operation fail if > you're not on any branch; iirc, if you try that now, it just silently > *succeeds* without uploading anything at all, which is one reason I so > frequently screw it up. Sounds workable. > Alternatively, is there a reason I can't > upload an object *without* giving it a branch name? I guess that > would cause problems with garbage collection. You've answered your own question there. >> There is also a Google Summer of Code project for this - see >> http://git.or.cz/gitwiki/SoC2008Ideas#head-9215572f23513542a23d3555aa72775bc4b91038 > > ok. I was hoping it wouldn't be so hard as to require an entire SoC > project, since using --alternate when checking out the child repo > shouldn't be too hard. If you think it is simpler, then I'm sure that submodules users would appreciate you sharing your ideas as a patch. Sorry if I am starting to sound like a parrot ;-). Sam. -- 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
