Re: Breaking up a monolothic repository

> Have you checked if the users have/need anything (emails, ticket
system, etc.) that refer to specific revisions or the history of
changes made there? It seems kind of drastic to throw that away
because you think the numbers aren't pretty enough.

But keeping thousands of empty commits in a project they're not relevant to
is confusing and wasteful. The repository and repository URL's for the old
project should be preserved, if possible, locked down and read-only,
precisely for this kind of change history. But since the repository is
being completely refactored *anyway*, it's a great opportunity to discard
debris.

Even if the history is considered sacrosanct (and this is often a
theological policy, not an engineering one!), an opportunity to reduce the
size of each reaporitory by discarding deadwood at switchover time should
be taken seriously.
Received on 2013-09-10 13:23:34 CEST