Re: [RFC 2/2] Don't push a repository with unpushed submodules

Hi,

On Tue, Jun 28, 2011 at 01:43:18PM -0700, Junio C Hamano wrote:

Heiko Voigt [off-list ref] writes:

quoted

quoted

What if

 (1) you are binding somebody else's project as your own submodule, you do
     not make any local changes (you won't be pushing them out anyway),
     and you do not have remote tracking branches in that submodule
     project?

In this scenario the superproject can not be cloned that way that it
would contain the submodule right? I would consider this a rather exotic
way to work since pushing means to share your work somehow.

Sorry, I don't follow. Isn't this the classical example of an el-cheapo
router firmware project (i.e. superproject) binding unmodified Linux
kernel project as one of its submodules without you having any push
privilege to Linus's repository, which was one of the original examples
used in the very initial submodule discussion?

But in such an example the Linux submodule (if used with git submodule)
would have remote tracking branches even though they are not directly
pushable.

Cheers Heiko