Ron Savage

You might also want to check out git-subrepo as an alternative: https://github.com/ingydotnet/git-subrepo

I've never used git sub-modules before, but that blog post makes it sound icky.

Any time I've had to share Perl code between repositories, I've been an advocate of:

1) putting the shared code in it's own repo,
2) packaging tagged versions as distributions with a tool like Dist::Zilla, and
3) incorporating the package into the consuming repos as I would any other third party dependency.

If the above steps haven't been possible, it was usually because the design of the shared code was messily coupled to the consuming application and either needed to be refactored or had no business being shared (in which case it seems better to copy => paste => permanently fork).