On Sun, 2010-04-25 at 13:11 +0300, Petteri Räty wrote:
> On 04/25/2010 01:06 PM, Ryan Hill wrote:
> > On Sat, 24 Apr 2010 20:40:54 +0300
> > Petteri Räty wrote:
> >
> >> What do you think about not allowing commits to eclasses without
> >> mentioning an another developer who has reviewed and appr
On 04/25/2010 07:36 AM, Ryan Hill wrote:
People make mistakes.
Agreed - at work I've often found a quality mindset that is 100% focused
on preventing mistakes, and I've found that these kinds of systems are
almost equally as focused on preventing them from being fixed (three
minutes to fix a
On Sun, Apr 25, 2010 at 4:36 AM, Ryan Hill wrote:
> On Sun, 25 Apr 2010 13:11:11 +0300
> Petteri Räty wrote:
>
>> On 04/25/2010 01:06 PM, Ryan Hill wrote:
>
>> > I think it's a good idea to strongly encourage it, but actually forcing it
>> > through cvs? No thanks. I'm not tracking down another
On 04/25/2010 01:06 PM, Ryan Hill wrote:
> On Sat, 24 Apr 2010 20:40:54 +0300
> Petteri Räty wrote:
>
>> What do you think about not allowing commits to eclasses without
>> mentioning an another developer who has reviewed and approved the diff
>> in the commit message? There's enough people on ge
