Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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 ;-) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
