Hi Ted, On Fri, 20 May 2011, Ted Ts'o wrote: > Lukas, are you going to be providing a new version of these patch > series or not? I already did send it as a separate patch series with the version description. > > If you are, could you do it as a separate patch series, instead of > only updating one patch as a reply to the mail thread. When people do > this, I find it painful since I need to figure out, "ok, I need v2 of > the 1/4 patch, v3 of the 2/4 patch, v4 of the 3/4 patch, and v3 of of > the 4/4 patch. To provide context, please add version descriptors > after the --- of the patch. (i.e, "v3 --> v4; fixed commit message") > > Also, if we're going to be doing extended review of patches like this, > instead of my just fixing things up when I pull stuff in, people need > to start authoring patches ***much*** sooner. Doing multiple publish > and review cycles now that the merge window is open really doesn't > work. One way of solving this in the future is to simply not take any > patch that is first submitted after say, -rc5 or -rc6 until the next > merge window. But given that some patches didn't *start* getting much > review until 2-3 weeks ago, that wouldn't be entirely fair. We all should do better, but I am not sure that limits like that are very useful. Some level of flexibility is always needed. > > But for the next merge window, if this is going to work, we need > people submitting patches earlier, and people reviewing patches > earlier. So let's to that people ;). > > Thanks, > > - Ted Thanks Ted! -Lukas > -- > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
