Hi Ian, On Thu, Sep 29, 2016 at 10:27 AM, Ian Boston <i...@tfd.co.uk> wrote: > ...I think it would be a mistake to attempt to split the repository into 100s > of separate Git repositories as it will make it near impossible for any > outsider to work on the code base....
My understanding is that one Git repository per released artifact is the standard way of working with Git, and having a single repository with our about 300 modules wouldn't be practical for releasing, tagging etc. And tools like those listed at [1] (repo, gitslave etc.) allow for creating a single "kitchen sink" setup to make it easy to checkout the whole codebase with one command. We should of course test that first before migrating, by doing a few dry runs of the conversion to multiple git repositories and tests of the resulting setup. Would that work for you Ian, or do you still think that won't work? -Bertrand [1] https://cwiki.apache.org/confluence/display/SLING/Move+from+Subversion+to+Git
