On Sat, Dec 10, 2011 at 1:30 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > So that use case does not sound like a good rationale to require addition > of floating submodules. Ok I will try another scenario :) Imagine again products A, B and C and a common library. The products are in a stable state of development and track a stable branch of the common lib. Then imagine an important security fix gets made to the common library. On the next pull of products A, B, and C they get this fix for free because they were floating. They didn't need to communicate with the maintainer of the common repo to know this. In fact they don't really care. They just want the latest stable code for that release branch. This is how package management on many linux systems works. Dependencies get updated and all products reap the benefit (or catastrophe) automatically. -- 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