[llvm-dev] Subprojects, GitHub, and the Monorepo

[Anton Korobeynikov via llvm-dev]

> The current proposal as I understand it recommends sparse checkouts to
> work with something less than the full monorepo.  I don't have any
> experience with sparse checkouts and we're unlikely to use it so I can't
> really comment on how useful it is, except it will prevent the two
> scenarios above and therefore seems good to me.
Well, sparse checkout affects only checkout. It does not affect clone
size, directory layout, history, etc. So, this means that downstream
users will still have to merge the whole monorepo somehow and tweak to
their needs (e.g. via manual history editing or force removal of
unnecessary projects). To my opinion this will create lots of problems
to downstream users unless we will provide them working solution (=
scripts) how to essentially replicate the current workflow with the
new monorepo.

-- 
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University