Re: Sparse checkouts suggestion
> 2. Previously I forked a medium-sized Monorepo on Github, and did the the
> complete expand/contract work for it - https://github.com/paul-hamm
> ant-fork/jooby-monorepo-experiment - in Python.
LOGIBALL's Tim Krüger has just written about a deployment of an
expanding/contracting monorepo for Git and Maven based on the above proof
of concept: https://timkrueger.me/a-maven-git-monorepo/ (I'd helped him
with the article).
There's are two Git realities that have to be closely monitored for teams
wanting to do trunk-based development in a monorepo:
1) the clone-size has an upper limit (accounts differ as to where that is)
2) there's a push-pull bottleneck when the team starts to attempt to push
at the same time (Git makes you pull stuff you don't have before you push)
Subversion doesn't have to consider those year-on-year. It does of course
have merge snafus that Git doesn't have. Then again Git has merge snafus
that Svn doesn't have - at least for creative branch use, IMO.
Received on 2017-09-21 12:16:25 CEST
This is an archived mail posted to the Subversion Dev