------ =_NextPart_001_01BDEC76.98030DF8
Content-Type: text/plain
> I think it would help matters all around if there were a web page
somewhere
> listing pending patches and even as little as a one-line comment from
you
> as to where they are in the integration process. It might even help
you
> organize your own work better.
-> This sounds extremely simple and very plausible. At least to
have a
-> visible patch queue on the web, ftp, or whatever else.
->
-> The best way to do this that I can think of at the moment would
be
-> to have a mailing address where patches are sent that is then
converted into
-> a simple web page that lists email address the patch originated, any
line
-> that has 'DESC:' at the beginning of it, and a link to either the
actual
-> email or just the patch itself.
->
-> This email address could also receive linux-kernel mailings and
do
-> the same thing w/ emails from that list that include patches.
->
-> This email address could also CC: Linus everything it receives
so
-> that even if this was not a plausible way for Linus to traditionally
receive
-> patches others could use it to see what people have submitted, and
perhaps
-> Linus could check it to see if some things didn't make it to him.
->
-> This could also promote wider testing of new patches before they
hit
-> the mainstream, and in fact digests of the list could be sent out to
those
-> that request it.
->
-> I'm fully aware that linux-kernel already does many of these
things,
-> but I suspect not all patches are cc:'ed to linux-kernel, and not all
patches
-> submitted to linux-kernel are intended to be incorporated into the
actual
-> kernel, so it might be best to keep these two seperate.
->
-> If there is alot of backing for this I'd be willing to put forth
the
-> effort to set up this system, unfortunately due to my limited
bandwidth I
-> would not be able to host it however.
If this is something that the community decides to do, then I _might_ be
able to provide a server and link to host this beast.
If this is something that I should put some time/effort into
accquireing, then please mail mail me directly (jesper@testhouse.dk
and/or jesper.juhl@infosport.dk) as I don't read Linux_kernel on a daily
basis.
Just to be on the safe side, I'll say this in advance: I am quite sure
that I can provide this, but please don't be upset if I should fail!
Kind regards
Jesper Juhl
------ =_NextPart_001_01BDEC76.98030DF8
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
> I think it would help matters all around if =
there were a web page somewhere
> listing pending patches and even as little as a =
one-line comment from you
> as to where they are in the integration =
process. It might even help you
> organize your own work better.
-> This sounds extremely =
simple and very plausible. At least to have a
-> visible patch queue on the web, ftp, or =
whatever else.
->
-> The best way to do =
this that I can think of at the moment would be
-> to have a mailing address where patches are =
sent that is then converted into
-> a simple web page that lists email address the =
patch originated, any line
-> that has 'DESC:' at the beginning of it, and a =
link to either the actual
-> email or just the patch itself.
->
-> This email address =
could also receive linux-kernel mailings and do
-> the same thing w/ emails from that list that =
include patches.
->
-> This email address =
could also CC: Linus everything it receives so
-> that even if this was not a plausible way for =
Linus to traditionally receive
-> patches others could use it to see what people =
have submitted, and perhaps
-> Linus could check it to see if some things =
didn't make it to him.
->
-> This could also =
promote wider testing of new patches before they hit
-> the mainstream, and in fact digests of the =
list could be sent out to those
-> that request it.
->
-> I'm fully aware that =
linux-kernel already does many of these things,
-> but I suspect not all patches are cc:'ed to =
linux-kernel, and not all patches
-> submitted to linux-kernel are intended to be =
incorporated into the actual
-> kernel, so it might be best to keep these two =
seperate.
->
-> If there is alot of =
backing for this I'd be willing to put forth the
-> effort to set up this system, unfortunately =
due to my limited bandwidth I
-> would not be able to host it however.
If this is something that the community decides to = do, then I _might_ be able to provide a server and link to host this = beast.
If this is something that I should put some = time/effort into accquireing, then please mail mail me directly = (jesper@testhouse.dk and/or jesper.juhl@infosport.dk) as I don't read = Linux_kernel on a daily basis.
Just to be on the safe side, I'll say this in = advance: I am quite sure that I can provide this, but please don't be = upset if I should fail!
Kind regards
Jesper Juhl
-
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/