Re: organizing multiple repositories with dependencies

From: username localhost <username.localhost@gmail.com>
Date: Apr 28, 2012, 17:31 UTC
Message-ID: <loom.20120428T191337-86@post.gmane.org>
In-Reply-To: <nngobqg1ztl.fsf@transit.us.cray.com>

dag writes:

Show 6 quoted lines

> 
> Should gitslave be covered in this document if gitslave is not in the
> upstream git repository?  I'm not knocking gitslave, in fact I think
> it's cool technology and probably _should_ be contributed upstream.  I'm
> just asking the question about whether stuff in Documentation/ is or
> should be limited to things in the upstream repository.

I think that it would be better to be inclusive while initially writing such a document. The work of helping to distinguish gitslave from the others should also help to flesh out the differences between submodules and git-subtree.

Once the document is in good enough shape that it can be merged, it would be easy enough to strip gitslave out if it were decided that it should not be included.

> 
> How about creating a topic branch for this and publishing it so several
> of us can collaborate?  I think that would make things a bit easier
> moving forward.

I second that. As a git user, I would love to see a document that described these systems, explaining how they differ, showing how various "common" actions are done in each, and describing the workflows each is best in, and what workflows each does poorly with.

If somebody does not create a branch and post a starting point, I'm afraid this idea will simply die out.

-- username@localhost