Question about handling of heterogeneous repositories

Hi,

it is sometimes the case that a project consists of parts which are unrelated to each other, and only thing in common between them is that they all are used in that particular project. For example a program uses some library and the developer(s) of that program would like to have the source of that library somewhere close. Well, for this simple example one could just use two repositories, laid close to each other in a directory, like project/lib and project/prog. Now, if I make the example a bit more complex and say, that the developers of the program are the developers in that project and change everything under project/ directory, including project/library/. They are also good people and ready to give the changes to the library upstream.

How do they achieve that, without sending project/ and project/program/?

For everyone who have an experience with ClearCase or Perforce (I'm sorry for mentioning it) it is what the "mappings" are often used for: a project is build together from different parts, which can be worked on separately.

I'm trying to introduce git at work, but have to prepare myself for possible questions first, and this is one of them :)

Greetings, Alex Riesen