Hi, On Fri, 25 May 2007, Sven Verdoolaege wrote: > On Fri, May 25, 2007 at 03:16:56PM +0100, Johannes Schindelin wrote: > > And the point about my config being private still stands. You have no > > business looking into my config. > > Put your private configuration in config and your public configuration > in submodulesconfig. > A public repo typically wouldn't have any submodules configuration > in config (or any other private information for that matter), but > we wouldn't read it anyway. Why complicate things? The information you want to put into submodulesconfig is an information you would most likely want to give cloners. And as it happens, we _have_ a perfect transport mechanism for clones. You only have to put the information into the object database itself, and -- voila -- no need to change any core level plumbing. That's why I keep harping on .gitmodules, since it _is_ the obvious correct, simple and elegant way to do things here. So, just "s/\.git\/submodulesconfig/.gitmodules/g" in your head, and you're done. Ciao, Dscho - 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
