Well...we should ask Linus what he'd like to do: If he saves a patch and
actually uses the patch, then we could have JB add a section to the patch
that creates a shell script someplace where Linus can execute it and
respond to the question "Accept it? (y/n)" or something similar.
On the other hand, we could set it up so that there is some other email
solution (replying to one of two mail messages) or something.
I have to admit that using some of the "auto-filetering" and
"auto-checking" schemes mentioned elsewhere does sound interesting (I
admit it, I love cool things like that), but the part that makes it most
interesting is that we can *automatically* add a layers of administrative
support before it hits Linus.
Things like send Document patches here, adding warnings about how many
files/directories patched, etc.
The goal is, after all, to make Linus' life more to his liking (whether
that's easier and productive, or otherwise).
Ciao!
docwhat@gerf.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/