In message <20101208205846.GW29789@xxxxxxxxxxxxxxxxxxxxx>, Oliver Kullmann writ
es:
I thought that "git submodule" would solve the problem, but now I
realised that these submodules are not "real", but they only
contain a bit of meta-data (this should really be said directly in
the documentation).
So my hope, that I can have one super-repo, where I say, e.g.,
"git submodule foreach pull", get the full super-repo, copy it on
a memory stick, and then by pulling from that copy I get
everything into another super-repo, from which I distribute the
sub-repos, seems not so easily realisable with git?
gitslave may work for you better than git-submodules in this specific
use case. http://gitslave.sf.net
In your example, you would create an organizational super-project git
module which is primarily a container for the .gitslave file which
tells the system how to access the various git repos and their on-disk
path names.
Given your diverse repo locations, it sounds like you will not be
using the feature which allows the pathnames of the slave repos to be
relative based on the URL to the super-repo (though you could have a
mixture of relative and absolute URLs if that would help your
functionality).
You would then run `gits pull` to issue a `git pull` against every
slave repo, and likewise `gits push` or `gits push home` or whatever.
(remotes would best work if your gitslave system has relative URLs).
While the super-project cannot be bare, the slave-repos could be bare
if that would help your data transfer functionality.
If certain slave repos would not be accessible in all locations, there
are options to bypass the errors you will get attempting to contact
the unreachable repos.
If you have any questions, please let me know (here, private email, or
on #git).
-Seth Robertson
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html