You're right. But with the fork you waste space for something what is in a private repo just a reference to a public repo. I don't want to make the security model of github a swiss cheese. I thought a submodule is an implicit fork of another repo.
On Oct 7, 6:12 pm, Cynthia Kiser <[EMAIL PROTECTED]> wrote: > Quoting Fritzek <[EMAIL PROTECTED]>: > > > About the 'git submodule remove' command: wouldn't it be cool on the > > other hand to have a pull request for submodules from whatever type of > > repo it comes (means pull request from private repo regarding the > > submodule)? > > Perhaps I am missing something, but that seems to me that it would > violate the security model for private repos, so I would say 'no, it > doesn't sound cool'. That's why I went with the public submodule fork > for the things I want. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to github@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
