Re: organizing multiple repositories with dependencies

In message <4F970C92.3030704@web.de>, Jens Lehmann writes:

    gitslave: This creates a federation of full fledged git repositories which
    are operated on by the gits commands together (where a git command would
    only operate on the superproject).
    The emphasis lies on the simultaneous operation of gits commands on all
    git repositories.
    It does not provide any coupling of the commits in the superproject and the
    slave repositories (but you can use tags to have that at some points in the
    history).

Well, gitslave is essentially a loop to run the listed git command in each repository, so there are no atomic operations and you can get partial success and partial failure, thus "simultaneous operation" isn't a very good description.

Perhaps a better sentence would be, "The emphasis lies in the simplicity and convenience of having gits commands run the same git operation on all linked repositories, with output summarizing."

Just a FYI: partial success and partial failure in different repositories isn't a major problem when using git. However, in the interest of full disclosure, two users racing to push could in theory cause a broken project given specific combinations of some users modifying different repositories than others with mutual dependencies between them. But in all of the years of using gitslave no-one has ever had/reported such a problem. If you can assuming any sort of sane QA and deployment practice, this should be able to cause an operational problem.

					-Seth Robertson