Whole tree up to date before committing

[Philippe Lhoste]

On 22/10/2009 18:29, John Arbash Meinel wrote:
> If you have a large amount of code with unrelated things, the
> recommendation is to split that up into separate projects (with their
> own collection of branches). With clearly defined boundaries of what
> files should stay synchronized. (If it is truly unrelated, then it
> should be in a different branch.)

While the advice is good in general, it is probably very hard to apply on large legacy 
projects.
Like the one we have at my work (we use Perforce... and yes, we can break the build too!), 
which is a large Java project with actually several independent (but with dependences) 
parts but quite blurry frontiers: it would take quite a big work to separate the 
sub-projects. Again, a desirable goal, but hard to put without making a major new version 
that can break...

So migration of big projects from other VCS can be delicate.

-- 
Philippe Lhoste
--  (near) Paris -- France
--  http://Phi.Lho.free.fr
--  --  --  --  --  --  --  --  --  --  --  --  --  --