> Also, final comment: if you _have_ sent patches to me, and they didn't
> show up in a kernel and you heard nothing back about why they didn't show
> up, please don't despair - re-send them instead (possibly with a longer
> explanation of why you want them in the standard kernel).
When you reject a patch (or for that matter, when you don't), it would
probably be nice to write a quick note saying why (user-space problem, messy
solution, "OK, but there's this really cool thing that I've been meaning to
do that would fit nicely with this..."), so the submitter knows how to
rework their patch (or eventualy wether to re-submit if if they don't get a
message from you in a bit or eight)...
> I'm afraid that
> some of my mail does tend to disappear: not because of unreliable email
> per se, but simply because I get a lot of it and if I'm busy doing
> something else I often overlook email I shouldn't overlook (but once it's
> been overlooked I -very- seldom have time to go back to old email).
You might want to make a folder of kernel-patches to take a look at
when you get a half-second (such as when you are waiting for a compile...
Assuming that you're still using a computer that takes non-negitive time to
compile.)
>
> Linus
>
-=- James Mastros
---
When the annals of distributed computing are written, and the name 'Bovine'
appears in there, I can say "Hey, I was a part of that, I checked .0012% of
the keyspace".
-=- Brian Wilson <wilsonb@mindspring.net>
Go to www.distributed.net before I come make you!