why no new 2.5-dj patch ?

[Dave Jones]

I'm fed up of answering the same questions over and over,
so I figured I'd post this here.

Most common question I'm getting right now seems to be summed up
as "Why haven't I done a 2.5-dj since .27 ?" (Yup, a whole 2 point
releases, and people are breaking into a sweat)

* Due to the huge driver breakage during .28/.29/.30tobe,
  Compilation issues aside, I've not had much luck in even
  getting the last few kernels to boot on most of my test boxes.
  If I don't get a 2.5-dj booting on all my test boxes, I won't
  make it available.

* Lack of time.
  I've been busy with x86-64, and other projects.

* Vacation.
  As of Friday, I'm taking time out for a real holiday for the
  whole week for the first time in a year. Ie, no net connection.

The last point marks an important change in the way I've been
working up until now. I spent a while trying to figure out
how to take a holiday, and not have to come back to a nightmare
resync. FSF purists will hate me for it, but I've started playing
with BitKeeper again, and it's working out.
(The curious can look around at http://linux-dj.bkbits.net)

I've put off pushing bits to Linus this week to deliberatly
make life more difficult for myself syncing his latest tree
with mine, to see if bk really will work out. So far what usually
takes me the better part of an hour I can now do in 10 minutes.

So when I come back, resyncing should be a lot less painful than
it used to be, and I'll start looking at pushing some of the bits
that have been hanging around for a while towards Linus.

One final point: Due to me being away for a week, I won't be
merging anything new to my tree 8) Feel free to still send it,
and I'll pick it up when I return.

		Dave.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs