On Thu, May 17, 2007 at 11:49:12AM -0700, Junio C Hamano wrote: > > Instead, why not: > > 1. url location is supplied in configuration as > > [subproject "kernel/"] > > url = git://git.kernel.org/pub/linux-2.4.git > > 2. .gitmodules is simply read as a lower-priority version of > > configuration > > That does not support seeking back and forth between appliance > release #1 and release #2 which wants to say they want to bind > two different things at the same kernel/ path, does it? I had a vague notion that the subproject could hold _both_ of them, since it's really the commits you're flipping between. But obviously that has quite complex semantics, so now it's me doing the handwaving. What is the planned behavior when doing such a switch? I.e., if I have kernel/ bound to linux-2.6, and I do a 'git-checkout' back in time to a version that wants linux-2.4 bound at kernel/, what will happen? Blowing away my subproject repo doesn't seem right. -Peff - 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
