Hi, On Wed, 2 Dec 2009, Ilari Liusvaara wrote: > And if mappings http -> curl, https -> curl, ftp -> curl are to remain > explicit in main git binary, I would put them into table and build stub > remote-curl if NO_CURL is defined instead of special casing the error in > main git binary (but I consider that worse than just removing the > association from main git binary). This is definitely a good direction, and it would be even better if the absence of the remote helper was also handled gracefully. Just think about a (as of now fictious) git-remote-http.rpm relying on git-core.rpm and libcurl.rpm. If you do not want to access http:// URLs, you can install just git-core. Once you encounter an http:// URL you need to access, you install git-remote-http. Keeping git-core. (I like to call this setup "modular".) Of course, I never understood why the backend should know the implementation detail that it is based on cURL, so it would be even more modular (at least by my definition) if there was no hard-coded mapping (Sverre -- Cc'ed -- seemed to like URLs of the form "svn::http://..."; and "cvs::pserver..." to trigger looking for a remote helper explicitely). I find the compiled-in mapping rather limiting. 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