You should take a look at git submodules. ��They are a little cumbersome but will likely satisfy your needs. ��Also, unlike svn, people tend to avoid having big git repositories that manage multiple projects. ��Each project typically has its own repository and is linked to others via submodules.
About piston:��if you want to modify your library in the context of one of your projects, there is no (easy) way to send the changes back to the library. ��This gets irritating fast.
On Sat, Jul 25, 2009 at 1:12 AM, Loqi <[address removed]>
Hey thanks, Jimmy and Jacob.
I guess I just have to learn all about how git to manage multiple copies of my code in sync. I think that means I should have a big git repository that contains all my little git repositories, and learn how to use git properly.
As to the Unix ln command, I'd use it if it would work on directories. According to this page,
Darwin breaks Posix standards and allows hard links to directories in the HFS+ filesystem. But I can't get it to work. Maybe they've since killed that idea because it's potentially dangerous.