Re: Submodules can't work recursively because Git implements policy?

On Mon, Apr 6, 2009 at 3:56 PM, Finn Arne Gangstad [off-list ref] wrote:

Yes, I could not agree more.  You may also end up writing some really
complicated wrappers around git push to get things going (where do you
push, for example). We made some interesting "concept art" around this
last year at $dayjob, but decided to drop it.

I don't see how pushing could work at all without recursion.

Maybe the security concerns could be handled by adding some
functionality to (quickly) get rid of unwanted commits?

Why not simply allow users with write permissions to "pop" revisions
from the top of the history DAG in a way that actually really deletes
the them? Or at least moves those commits to a separate, locked down
DAG that cannot be read by people without write permissions?

But anyway: If I implement support for fetching SHA keys and full
recursive behaviour in the presence of submodules; would my patches
automatically be rejected because of the rationale for the current
behaviour?

/Klas