Kristian Høgsberg <krh@xxxxxxxxxx> writes: > On Fri, 2008-04-04 at 11:24 -0700, Junio C Hamano wrote: >> Here are the topics that have been cooking. Commits prefixed >> with '-' are only in 'pu' while commits prefixed with '+' are >> in 'next'. >> >> The topics list the commits in reverse chronological order. >> >> With a handful topics graduated to "master", we hopefully will have the >> final 1.5.5 soon. > > What happened to builtin-clone? Nothing. > ... I know I just threw it over the fence, > but Daniel picked it up and got it a lot closer to working? Did it fall > through the cracks or is it just 1.5.6 material? If I recall correctly, "a lot closer to working" happened way after 1.5.5 merge window closed, so it definitely is not 1.5.5 material. 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'. So at this point, I optimistically say that it has a good chance of being deeply in 'next' and all the active git people would hopefully be using it, by the time 1.5.6 (or perhaps that is named 1.6.0, depending on what else we will do) ships, but I cannot say much more than that. It very much depends on how hard the code has been scrutinized already at this point; I haven't personally looked at it in any serious depth yet. -- 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
