> I am not sure what you mean by "static linking" anymore. Usually the word > means that everything you tell the linker to link to the executable is > linked, together with objects from libraries. The resulting executable is > usable on its own and it does not change behaviour regardless of which > version of dynamic libraries you depend on happen to be installed on the > target system (because by definition a statically linked executable does > not depend on dynamic libraries---that is the whole point of static > linking). > There seems to be no misunderstanding in the static linking - i meant the same thing. But let me put an example: I have a program.exe This program.exe is built basing on two statically linked libraries lib1.lib and lib2.lib I'm not developing any of those libraries, but only my own code of the program.exe Now, somebody changed 2 files in lib1.lib and 5 files in lib2.lib. But i don't know that they are changed because it is different CVS module or because I'm building against latest released libs or for whatever reason... When i rebuild my program the build supposed to pick up changes from the libraries I'm using and relink, that will include 7 changed obj files. How can i say which exactly files are changed in my new version of executable comparing to the previous version? Currently they can take a look at the revision number of every particular file included into the executable, which is put there by CVS and compare it with the production. If the version is different, then you know which files are changed and you can get diffs on them... They also have file path and date and other stuff expanded... Please note, my personal goal is *to prove that git can do that better*, with less intrusion into the code sources, not other way around.So, while keeping the info they want to have they might get some benefits of git. Although, i understand that there might be no cure for this state already, you can tell me that and I will close the topic, but I just keep hoping;) Thanks a lot, 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