[ANNOUNCE] fbdev git tree.

[Paul Mundt <lethal@linux-sh.org>]

As I find myself spending more time reviewing and merging fbdev patches
lately, and in an effort to offload some of the pressure on -mm, I've
opted to start a git tree to start collecting and merging fbdev changes.

I plan to get a patchwork queue established for the list as well so that
things don't fall through the cracks (the link will be posted once it's
been established). People will be able to see the status of their patches
this way, rather than wondering whether things are being picked up,
overlooked, or forced through an alternate merge strategy (We have had
reasonable success with this with the SH tree, so here's hoping that the
same approach will work well here, too).

I've already made a note about this to akpm off-list, so fbdev patches
that pop up outside of the regular channels that I may be unaware of
should still have a reasonable chance of being intercepted and rerouted
(although the mmotm is rather devoid of drivers/video churn at the
moment).

I'll be combing through the list archives to see if there is anything
glaringly outstanding (the HDMI/EDID work comes to mind) and working on
getting the oustanding issues there resolved. If anyone has any
outstanding patches that have fallen through the cracks, now would be a
good time to provide pointers!

Given the point that we're at with .38 bits now and a cursory look at
-next shows that there's already quite a bit of drivers/video churn
coming in from git trees. It will likely take a few cycles to get people
used to the idea of there being an active fbdev tree to merge through,
but with any luck it will be a fairly natural transition. I'll be
contacting and working with git tree owners separately so there aren't
any surprises.

The tree can be found at:

	git://git.kernel.org/pub/scm/linux/kernel/git/lethal/fbdev-2.6.git

Stephen, if you could add this with the master branch to -next, it would
be appreciated. For the moment I expect most of the patches to follow a
fairly linear line of development, but there may be cause for topic
branches as new (or contested) patch sets arise.