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

Message-ID: <20101026204043.GA2608@sig21.net>
Date:	Tue, 26 Oct 2010 22:40:43 +0200
From:	Johannes Stezenbach <js@...21.net>
To:	Ivo Van Doorn <ivdoorn@...il.com>
Cc:	"Luis R. Rodriguez" <mcgrof@...il.com>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Compat-wireless release for 2010-10-25 is baked

Hi,

On Tue, Oct 26, 2010 at 09:48:12PM +0200, Ivo Van Doorn wrote:
> For rt2x00 development you can choose between rt2x00.git and
> wireless-testing.git,
> the trees are usually not that far apart, since smaller patches are pushed quite
> quickly upstream. (Also rt2x00.git is rebased frequently, while
> wireless-testing.git rarely
> is rebased)

Thanks for clarification.  I guess I'll start with wireless-testing,
that sounds a bit more newbie-friendly.  I just want to avoid
searching or reporting bugs which are already fixed, but your description
sounds like changes are pushed from rt2x00.git to wireless-testing.git
maybe weekly.  I was afraid patches would be pushed to wireless-testing.git
only when it's time to get ready for the next merge window.

Thanks,
Johannes
--
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/