> But how often do you have a project that has no external or internal dependencies on any other packages or libraries? Any project I've ever done, big or small, has relied on some existing codebase. Imagine a project that uses liba and libb, which both reference libc. To use Git, I'd have to have copies of libc existing in three repositories, and copies of liba and lib in two repositories each. What a nightmare... and that's only a trivial hypothetical example. > ...> I'm really trying to get on the Git bandwagon, here. > > -- > Thomas Hauk > Shaggy Frog Software > www.shaggyfrog.com > For example at my shop we have very "component oriented" approach (JAVA). Each project is a separate git repository, that is producing one artifact (.jar, .war etc) and has a ivy dependency descriptor. We are using Hudson CI to perform intergration builds of projects themselves upon push and their downstream projects as well. In this particular example there is no need to keep any copies that you're talking about. For this Git works perfectly!! OTOH there is a part of development that is using C++. And the whole infrastructure is about static linking and is so heavily depending on the CVS ability to expand keywords, that there is no way (at least so far i could not find an acceptable solution) to migrate the C++ development to Git. My question is why do think you should have the copies??? Can it be that the inability to use Git for your projects is related to the way how you do things? May be you just have to be ready for the paradigm shift first hand? Thanks, Eugene -- 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