Strategies for push/merge problem?

[Sean Russell]

On Tuesday 15 July 2008 11:12:09 am Adrian Buehlmann wrote:
> >> "Cheap" commits doesn't mean they are allowed to be brain damaged.
> >
> > Sure it does. I practice test first design, so I commit tests that
> > break because the code isn't there yet.
>
> Well, there's no need to commit that. But obviously we have different
> mindsets. You seem to argue that "test first design" implies committing
> testsuite breaking changes. It doesn't.
>
> I wouldn't pull such a patch of yours into any repo I would be
> responsible for.
>
> Why would anyone else need your breaking test *enabled* in the
> testsuite without the code?

One of the requirements for proper test-first development is ensuring that the 
tests actually fail.  I can see a good use case for having that in the 
history. 

--- SER