[...]
> Some others here mentioned modifing pine to accept 'function-keys' w/
>automated replies that Linus could use to give developers faster
>feed-back, something like instead of hitting 'n' for next message he can
>hit 'F2' and a message will be fired off to the developer and JitterBug
>saying 'Seen it, too busy, will get back to it later', JitterBug could
>then registar that, mark it as 'PENDING Review' or something similar and
>could then send the patch again to Linus a week later w/ a note saying he
>said this was pending, now what?
Seems to me that a kernel release may happen during the week, so the
auto-sent patch could be outdated. Having the developer retransmit the
patch solves this. Or can Jitterbug auto-invalidate pending patches when
the release happens?
Helge Hafting
-
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/