Hi, On Thu, 24 May 2007, Petr Baudis wrote: > On Thu, May 24, 2007 at 11:35:33AM CEST, Johannes Schindelin wrote: > > Hi, > > > > On Thu, 24 May 2007, Sven Verdoolaege wrote: > > > > > On Thu, May 24, 2007 at 12:40:20AM +0100, Johannes Schindelin wrote: > > > > On Thu, 24 May 2007, skimo@xxxxxxxx wrote: > > > > > This patch series implements a mechanism for cloning submodules. > > > > > Each submodule is specified by a 'submodule.<submodule>.url' > > > > > configuration option, e.g., > > > > > > > > > > bash-3.00$ ./git-config --remote=http://www.liacs.nl/~sverdool/isa.git --get-regexp 'submodule\..*\.url' > > > > > submodule.cloog.url /home/sverdool/public_html/cloog.git > > > > > submodule.cloog.url http://www.liacs.nl/~sverdool/cloog.git > > > > > > > > I am sorry to complain so late in the game, but I am not really interested > > > > in submodules. However, what you say here is not a task for git-config > > > > IMHO, but rather for git-remote. > > > > > > Hmmm... git-remote does only local configuration and never gets > > > any information from the other side. > > > What would be the interface and how would you get the information? > > > > I was complaining that git-config, which is purely a local beast, gets > > infected with even more obscure stuff. Junio mentions regularly that he > > does not trust git-config that much, and given the number of fixes we > > still get, I have to agree. So let's not put any more stuff into that > > kitchen sink, especially if it has nothing to do with the configuration of > > your repo. > > Then again, git-remote is purely a local beast too, isn't it? No. Think "update" and "prune". Both access the remote site. > We could use git-remote-config for accessing remote configuration (if > it's a good idea at all, which I'm not totally convinced about)... (And > hope people don't confuse it with stuff related to git-remote too much.) As Junio _already_ said, people have no business looking in other people's configuration. If you have something to publish, do so. But don't make the tool publish _everything_ by default. 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
