Jay West

Thank you for the feedback. I have been kicking the tires of git meta off and on and have been trying to sell the idea within our company for quite...

This doesn't seem like valid usage. There is no submodule structure to begin with.

Different histories are actually desired. meta_repo1 and meta_repo2 would be independent. The important thing is that they don't interfere with each other in the common submodules.

I read through the architecture doc in detail. Maybe I'm missing something, but how is this different from your local repo branch pointing to one commit, and the remote repo...

Yes, I see the race condition/atomic problem across multiple repos if you actually try to push updates to branch heads. I'm thinking more along the lines of a synthetic meta...

We have a fairly large organization with multiple business units and multiple product groups within each business unit. Each product group has its own set of git repositories. We want...

> What happens if two people try to push a hotfix to the same branch at the same time? The architecture doc describes a possible race here: if each of...

The problem is when we have some people using git-meta and some not. How does a meta-user push his commits back to the subrepo so that the non-meta-user can see...

Yes, I think that would do the trick. The local tracking of branch history is not needed. Git meta open should also read this branch and set the subrepo to...

For consistency problems, a warning would be sufficient and it's ok to leave it to the user to resolve. Right now, we use the deprecated "git-slave", and if a push...