GIT_OBJECT_DIRECTORY ignored when cloning submodules

Hi,

In the pursuit of optimizing meta-repo workflows, I wanted to use GIT_OBJECT_DIRECTORY to specify a single objects directory used by all repos and submodules on a workstation.

The idea being that many metarepos will contain similar sets of submodules, and objects can be reused, thus potentially saving massive amounts of disk space and network traffic.

However, when cloning a repo with submodules, the variable is cleared when the submodules are cloned recursively.

Is this a bug, or intentional?

Thanks, Robert Schmidt

Robert Schmidt-Cisternas <robert@schmidt-cisternas.net> writes:

GIT_OBJECT_DIRECTORY applies to the source object store, not the target object store---clearing is very much intentional, I think.

An operation like clone, fetch and push can involve two object stores (iow, you can do them between two repositories on the same machine using local transport), and allowing both sides to use the same GIT_OBJECT_DIRECTORY would probably not make much sense.