Git submodule commits

[Martin Terra <martin.terra@koodaripalvelut.com>]

Hi!

We have git repository A and B.

A depends on B.

The team working on B has no visibility to A.

However, team A has visibility to both A and B.

You can think of it as if repository B is outsourced.

Now when team A is working on features and make a change which affects
also B, ideally there would be a single (single index)
commit/pull/etc. across A and B. Ideally, there would be no duplicate
copies of artifacts, i.e., optimally something from B commits only to
B and something form A only to A (think Submodule but with ability to
commit also).

How can this be accomplished using Git or is it a missing/planned
feature in git, or is there a 3rd party tool that helps with this?
Submodule and subtree don't seem to have these capabilities, or do
they?

Currently we have these set up on cvs and committing across projects
works effortlessly, but cvs is in many other ways outdated.

Related topics:
- https://jira.atlassian.com/browse/BSERV-4577


Thanks.

**
Martin