"Most people probably will not notice the changes. One big change from -rc10 is that there are tar-balls and patches, so if you aren't a git user (why?) you can download it now in a traditional format. On of the things to note is that the files are now signed by my gpg key, and it's the *uncompressed* version that the signature is for.

"And of course, this means that the merge window for 3.2 is open. I'll do some merging during the KS, but probably most when I get back home - but you can still send me the pull request, even if I may not necessarily pull it for a few days.

"NOTE! Because the -rc series was longer than usual, and as a result linux-next is bigger than usual, I'm going to be much more of a stickler for 'has your patch series been in linux-next' than usual. If I get a big pull request for things that I can't find in my linux-next branch, I will simply not pull it - we have enough code that has gone through the proper channels as it is, and we don't need anything extra.

"Another thing worth mentioning is that I really want the pull request to be validated some way. With the small changes late in the -rc series, I could afford to spend the time to look at commits and try to verify them, but with the merge window (and the 11k commits or so that I saw pending in the last linux-next tree), that just isn't reasonable.

"So use git.kernel.org or some other host that I can trust is really you.