Re: Breaking up a monolothic repository

Nico Kadel-Garcia <nkadel_at_gmail.com> writes:

> Lock the existing repo: Do clean exports, and imports, to new repositories
> with the new layout, with a README.md or other guideline to where the
> legacy repository exists. You lose the infinitely preserved history this
> way, but for most working software projects, you don't *need* that. And
> it's a good opportunity to discard materials, such as bulky binaries or
> security sensitive files with plain text passwords.

Ah, sorry, I forgot to mention that preserving history was a hard
requirement handed down from higher up.

I get the impression that $company's projects mostly have a finite
lifespan (a couple of years), so I think that approach ends up being
very similar to my current plan of creating new projects as new repos,
and letting the monolithic repo die out via attrition.

I don't actually know exactly what they put in their repos; I think it's
about half "huge unpacked source tarball I downloaded from somewhere
then tinkered with" and half huge CAD files and .docx contracts.
Received on 2013-09-09 04:17:35 CEST