On Fri, May 21, 2010 at 6:28 PM, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote: > On Fri, May 21, 2010 at 5:44 PM, Luis R. Rodriguez > <lrodriguez@xxxxxxxxxxx> wrote: >> Sometimes you have no other option but to carry around patches. >> This can happen for a variety of reasons. Ultimately testing of code >> cannot happen on the kernel maintainer's clock but on your own. >> >> This expands the idea of the linux-next-cherry-pick patch directory >> on compat-wireless to also allow for patches to be merged which are >> posted to some mailing list but pending merge due to some reasons >> (merge window is a good example). It also adds a crap patch directory >> for those really nasty situations you can run into where you have >> no other option but to give someone a release with some delta even >> if the patch is not yet posted anywhere. >> >> The focus should always be upstream though so to avoid these >> situations we will also provide code metrics to indicate to >> the package maintainer how much code came from each directory, >> including the backport code to support older kernel releases. >> >> Maybe we should add the code-metrics.txt file as a print out >> on the compat module load :) >> >> Signed-off-by: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> > > So this is what I get with what I just merged and using -p -c > > compat-wireless code metrics > > 497275 - Total upstream code being pulled > 1393 - backport code changes > 1163 - backport code additions > 230 - backport code deletions > 0.28 - % of code consists of backport work I just realized this % is wrong as it only accounts for the *.patch files for the backport. We'll have to exlude compat/ dir for the code calculations and add the code there for the backport calculation. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
