On Fri, 27 Jul 2018, Ramana Radhakrishnan wrote: > Joseph, > > A lot of such information seems to come out from a number of reviewers > only during patch review from new contributors. Would you mind > improving https://gcc.gnu.org/contribute.html and especially around > "Testing patches" or start something like the glibc contribution > checklist on the wiki that actually makes a lot of this easy to find > rather than searching in mailing list archives for new contributors ?
I think the information in my comments about proper contents of the patch submission is generally already present in contribute.html. There may be less information about expectations for target architecture / OS maintainers running tests on an ongoing basis. Perhaps at the Cauldron we should discuss whether we wish to move towards a requirement of bots posting test results for all new architecture and OS ports? -- Joseph S. Myers jos...@codesourcery.com
