linux-kernel - Re: [PATCH] compat-wireless: add linux-next-pending, crap patch dirs and nagometer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 May 2010 18:28:19 -0700
From:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
To:	linux-wireless@...r.kernel.org, linux-bluetooth@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org,
	"Luis R. Rodriguez" <lrodriguez@...eros.com>
Subject: Re: [PATCH] compat-wireless: add linux-next-pending, crap patch dirs 
	and nagometer

On Fri, May 21, 2010 at 5:44 PM, Luis R. Rodriguez
<lrodriguez@...eros.com> 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@...eros.com>

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
      6856 - Code changes posted but not yet merged
      4412 - Code additions posted but not yet merged
      2444 - Code deletions posted but not yet merged
      1.38 - % of code not yet merged
      1225 - Crap changes not yet posted
      1181 - Crap additions not yet merged
        44 - Crap deletions not yet posted
      0.25 - % of crap code

Base tree: linux-next.git
Base tree version: next-20100518
compat-wireless release: compat-wireless-20100521-3-g0935025

The 1.38% is code Atheros has posted but is not yet merged. By default
this code is not merged into the bleeding edge compat-wireless
releases.

Usage: ./scripts/admin-update.sh [ refresh] [ --help | -h | -n | -p | -c ]
   refresh - will update your all your patch offsets using quilt
        -n - apply the patches linux-next-cherry-picks directory
        -p - apply the patches on the linux-next-pending directory
        -c - apply the patches on the crap directory

In case it helps with the delay of the merge window feel free to send
me patches which are pending and you do think are important for
existing testing with the bleeding edge linux-next codebase. I am in
hopes as a side effect maybe this could help John and/or Marcel
*after* the merge window when they have to merge stuff for the next
release cycle.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/