RE: Preventing "Dirty" Checkins

[Jim.Hyslop]

address@hidden wrote:
> Yet another method is to divorce the notion of "latest 
> checked in" from
> "eligible for build".  I personally would never discourage anyone from
> checking in their work,
I actively encourage frequent checkins. If you have something that will (or
might) break the build, then create a private, temporary branch and check it
in there. The important thing is that your work is safe in the repository;
I've had a few too many hard drive crashes to leave it to chance.

-- 
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (http://www.leitch.com)
Columnist, C/C++ Users Journal (http://www.cuj.com/experts)