Well, I went to bed shortly after my missive :-)
> One header file disappeared in the email pile somewhere. Of course
> if you'd _bothered_ to check the l/k archive before ranting you'd
> have found the posting about it.
Hm. I got testy because there were three broken things I stumbled over
in 12 hours. I think this just highlights the need for BitKeeper or
equivalent, where automated regression testing (even a simple "does it
compile and link?") is performed, and if the test fails, it gets
bounced and doesn't even get to Linus.
Alan: I realise it's impractical for you to manually test each
patchlet that you send to Linus, since you carry a large number of
them. But would you consider an automated system? I'm thinking of a
script that you use to "mail" each patch to Linus. Said script applies
and compiles, and either bounces the patch, or sends it off the Linus.
That way you get the same fire-and-forget behaviour you have now with
email, but with better testing.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
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/