Larry, would it be acceptable/possible to regularly push some data/metadata
to sites like kernel.org that people already consult for kernel development ?
This way, Andrea's tool would only have to check kernel.org, and not bkbits.net.
Another solution is to fetch from a reverse proxy-cache on a high-bandwidth
site, provided that we know what to cache, of course. This could even reduce
your current HTTP usage since nearly everything should be cacheable for a very
You know, sometimes I fetch changesets from bkbits.net with my browser, and
I later convert them from html to text with a very trivial sed script. And it
happens that I remember you saying that the bandwidth costs you very much, then
I feel a bit guilty (although about once a week may not be too much) and I
wonder what would happen if everyone did the same regularly.
You may also try to cap the bandwidth from the web server, to dissuade people
from using it, but still not closing it. This could also help you not to pay
for the extra bytes.
Just some suggestions, of course. I wouldn't like your http service to be
closed since I sometimes use it.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/