Hi, On Mon, 4 Feb 2008, Steffen Prohaska wrote: > On Feb 3, 2008, at 11:43 PM, Johannes Schindelin wrote: > > > If your issue is with git-submodule, then fix _that_, and do not "fix" > > _anything_ else. > > If I understood Mark correctly, this would not solve his problem > because he wants to *avoid* origin; So he should *avoid* origin. Not redefine it. For example, if you want to update your submodules from their respective "bollywog" remotes, it is perfectly fine with me to introduce a notion $ git submodule update --from bollywog If you do not want to fetch from here one time, and from there the next, then there is _simply_ _no_ _point_ in pointing to another remote _name_. You cannot put multiple urls into .gitmodules _anyway_, so they _have_ to be modified locally, and then the people can look up their remote urls. Putting in another layer of indirection, which can very well be unsynchronised is what I am strongly in "unfavour" of. Frankly, I am puzzled how long this discussion drags on. If I would not be concerned about the loss of simplicity of git's core _and concepts_, I would not even bother to respond. 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