From: Junio C Hamano <gitster@pobox.com>
Date: Sat, 05 Apr 2008 05:51:53 GMT
Subject: Re: What's cooking in git.git (topics)
Message-ID: <7vmyo8yhl2.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <alpine.LSU.1.00.0804050221000.4008@racer.site>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Fri, 4 Apr 2008, Junio C Hamano wrote:
>
>> Judging from the fact that we recently had to deal with the fallouts of 
>> C rewrites that happened during the 1.5.4 timeframe, I would have to say 
>> that any C rewrite of a substantial and important program needs to be 
>> cooked at least for one (or preferably two cycles, especially we are 
>> trying to have shorter cycles) in 'next'.
>
> That would mean that you'd have to merge it into 'next'.  And rather 
> sooner than later, since everything else would lead to a dragging out of 
> the timeline.

Yes, which means somebody needs to present a mergeable history rather
sooner than later, and that somebody does not have to be me ;-)