[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 10:59:55 -0400 |
Maarten de Boer wrote:
> > One catch I can see with this approach is the platform. For
> example, our
> > development platform is Windows using Microsoft Visual
> Studio, and our
> > repository is on a Solaris machine.
>
> So, the testing machine could be Windows with Visual, which
> could compile,
> test, and move the "compiles-correctly" tag.
But that's a different approach from what was suggested. The suggested
approach was a commitinfo script. Commitinfo runs *only* on the server.
I'm not saying the suggested approach was the best, or even workable. I'm
just pointing out a potential problem with the suggestion.
--
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, 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, 2004/09/29
- RE: Preventing "Dirty" Checkins,
Jim.Hyslop <=