His patch file already has a bunch of patches glorped together. In theory
they could be separated again by parsing the mail headers. I suppose that
would be less work for Linus...
The point is, the difference between the patches WE get and the patches LINUS
gets is the granularity. He's constantly extorting other people to watch the
granularity of what they send him (small patches, each doing one thing, with
good documentation as to what they do and why, in seperate messages), but
what WE get is a great big diff about once a week.
So what I'm trying to figure out is if we can impose on Linus to cc: a
mailing list on the stream of individual patch messages he's applying to his
tree, so we can follow it better. And he IS willing to do a LITTLE work for
us. He's issuing changelogs now. This would be significantly less effort
than that...
MySQL is overkill, and since these things started as mail messages why should
they be converted into a foriegn format? There's threaded archivers for
mailing lists and newsgroups and stuff already, why reinvent the wheel?
Rob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/