linux-kernel - Re: Compat-wireless release for 2010-10-25 is baked

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-next>] [day] [month] [year] [list]

Message-ID: <AANLkTimzUKj=C9PxGs1PkQy_KWu0PGKd1zv_m-ZpWaEm@mail.gmail.com>
Date:	Tue, 26 Oct 2010 08:59:04 -0700
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	Johannes Stezenbach <js@...21.net>
Cc:	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Compat-wireless release for 2010-10-25 is baked

On Tue, Oct 26, 2010 at 5:35 AM, Johannes Stezenbach <js@...21.net> wrote:
> On Mon, Oct 25, 2010 at 03:03:57PM -0400, Compat-wireless cronjob account wrote:
>> From git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
>>    d9f241e..e10b307  history    -> origin/history
>>  + c8b020e...fd4f9b3 master     -> origin/master  (forced update)
>>    b515316..229aebb  stable     -> origin/stable
>>  * [new tag]         next-20101025 -> next-20101025
> ...
>> Base tree: linux-next.git
>> Base tree version: next-20101025
>> compat-wireless release: compat-wireless-2010-10-22-pc
>
> I wonder about the different tarballs in
> http://wireless.kernel.org/download/compat-wireless-2.6/
>
> compat-wireless-2010-10-25.tar.bz2
> compat-wireless-2010-10-25-p.tar.bz2
> compat-wireless-2010-10-25-pc.tar.bz2
>
> Those -p and -pc postfixes are not explained in
> http://wireless.kernel.org/en/users/Download

Right, sorry, I haven't updated the docs to add documentation for
them. First please read:

http://marc.info/?l=linux-wireless&m=128716953726075&w=2

-s is for getting and applying pending-stable/ fixes
-n is for applying the patches linux-next-cherry-picks directory
-p is for applying the patches on the linux-next-pending directory
-s is for applying the patches on the crap directory

> On a related note, I ran across compat-wireless-2.6.36-rc8-1-cs.tar.bz2 in
> http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.36/
> which is not linked on
> http://wireless.kernel.org/en/users/Download/stable/#Releases

That was sort of an RC release I made that I was waiting on feedback
on for some extra linux-next-pending patch merged but I was still
waiting for one test and no one got back to me yet on that. I'm just
going to go ahead and release a new tarball today.

> and I wonder about the -s and -cs postfixes?

This is the crap and the stable fixes propagated. I only had one crap
patch to incorporate though so I will move that to linux-next-pending
and we'll have at -ps release, which means one linux-next-pending
patch will be applied and we'll also get all pending stable fixes
merged.

> Can someone shed a light on this?

Hope this helps.

  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/