On Thu, Jan 31, 2019 at 12:05 AM Philip Oakley <philipoakley@xxxxxxx> wrote: > > On 30/01/2019 20:57, Ævar Arnfjörð Bjarmason wrote: > > > > * "Big repos". We had discussions about this in years past. It's a very > > spawly and vague topic. Do we mean big history, big blobs, big (in > > size/depth/width) checkouts etc? > > > > But regardless, many of us deal with this in one way or another, and > > it would be good to have a top-level overview of how the various > > solutions to this that are being integrated into git.git are doing / > > what people see on the horizon for scalabiltiy. I am also very interested in that topic ;-) > I'd also like a bit of discussion about ensuring that the partial clone > & filtering aspects of 'big repos' (if partial is needed /used then it's > big ...) still retain the full 'distributed' nature and capability of git. And in this too, especially regarding my work on many promisor/partial clone remotes (previously ODBs).
