lvu submit changed - now uses HTTP POST to deliver patch

[Duncan Gibson]

> currently the script notifies the user both when the patch got accepted or
> rejected. The script can also defer acceptance in which case it'll just
> sit longer in the queue.

OK, I just got an acceptance for a module I submitted earlier. Without the
mailing list feedback I was worried it might have gone astray while the
kinks are being straightened out. I suppose I'm just impatient.

> I hope to add some stuff to it that will either throw a summary out (to
> lunar-dev) for the current queue if there are items older than 24h in it,
> or post a weekly queue summary somehow.

My 2c would be to forward the submission to the mailing list like now.

> However, my goal is to review the queue on a daily basis at least and get
> feedback returned within such a time frame. How I'll do the above items I
> just don't know yet.

Cloning? :-)

I think if people get a mailing list acknowledgement, which is sort of
what happens now, they will be prepared to wait a little longer. Especially
if the submission queue is visible on a web page somewhere and they can
see that things are happening, even if not to their module right now.

Cheers
Duncan / engelsman