[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Preventing "Dirty" Checkins
From: |
Jim.Hyslop |
Subject: |
RE: Preventing "Dirty" Checkins |
Date: |
Wed, 29 Sep 2004 09:35:34 -0400 |
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)
- Re: Preventing "Dirty" Checkins, (continued)
- Re: Preventing "Dirty" Checkins, Todd Denniston, 2004/09/28
- Re: Preventing "Dirty" Checkins, Pierre Asselin, 2004/09/28
- Re: Preventing "Dirty" Checkins, Greg A. Woods, 2004/09/29
- RE: Preventing "Dirty" Checkins, Jim.Hyslop, 2004/09/29
- RE: Preventing "Dirty" Checkins, Jim.Hyslop, 2004/09/29
- RE: Preventing "Dirty" Checkins,
Jim.Hyslop <=
- RE: Preventing "Dirty" Checkins, Jim.Hyslop, 2004/09/29