Submitting BK patches...

[Jeff Garzik <jgarzik@mandrakesoft.com>]

Linus,

Continuing the BK lovefest a bit...  (hi Andrew)

Here's modifying my patch submission method a bit.  I have taken my
pending changes for you, and split them up into different BK clones. 
Each tree represents a different patch "theme", for different types of
patches being submitted to you:  net driver maintenance stuff is at
http://gkernel.bkbits.net/net-drivers-2.5, filesystem-related stuff can
be stored at fs-2.5, small driver fixes at small-fixes-2.5, etc.  This
gives you a more fine grain from which to 'bk pull'.

It also makes it easier on me as a maintainer, because I can (for
example) continue to push boring maintenance patches to net-drivers-2.5,
which leaving more controversial or unrelated trees untouched.  If you
want to ignore net driver merges for a couple weeks, I can keep pushing
release-quality stuff to net-drivers-2.5, and then you can just 'bk
pull' all the acculumated stuff.

In order to keep the community better in the loop, I'll post the
commented changeset summaries you get, as well as full GNU-style patches
for any changes worth comment.  (in the near future, I'm hoping I can
provide a URL to a plaintext GNU-style patch for each changeset, making
this stuff even more accessible to non-BK users)

The next two e-mails are examples which are ready to be merged.  All BK
changes from me are now under their own URL, http://gkernel.bkbits/... 
You'll note the "pull from" URL at the top of each changeset e-mail.

Comments and questions (from all) welcome...  I'm hoping this sort of
system will (a) make merging and review easier for you, (b) make ongoing
maintenance easier for me, and (c) keep all these changes visible and
easily available to people not using BK.

	Jeff


-- 
Jeff Garzik      | "I went through my candy like hot oatmeal
Building 1024    |  through an internally-buttered weasel."
MandrakeSoft     |             - goats.com