[racket-dev] proposal for moving to packages

Juan Francisco Cantero Hurtado wrote at 05/20/2013 11:20 PM:
>
> I also think that git submodules are a bad idea for packages. One git 
> repo per package is more simple and less problematic.

Do people expect to often do commits involving changes across these 
package boundaries?  If so, would another option be to keep a single 
repo, not use these Git submodules, and just have Racket translate the 
Git paths behind-the-scenes for packages coming from this core Racket repo?

Neil V.