just publish the git tree

I could care less if RH splits out all the patches into cute little patch files to make it harder for Centos, SL, OEL, or pick your favorite RHEL compat vendor to create a duplicate or slightly modified kernel with the RH generated rpmbuild system .. I just want to know what they are in their tree - so I'd argue (particularly since the RHEL kernels tend to be in heavy use) that the generated git trees should really be in kernel.org and if they really are pushing upstream (where some of their developers already live) they should have a for-linus merge branch against their entire tree .. why I see this as important has less to do with the contributed patchsets themselves but more to do with the integration point necessary for many 3rd party products - there's a larger infrastructure here that's in danger of collapse if RH starts closing it's doors out of competitive fear

now intentionally obfuscating the commit logs if that rumor is true .. is another matter altogether