On 4 July 2013 20:19, <pcha...@cs.wisc.edu> wrote: > > We want to contribute to GCC, but we are confused about the preferred work > flow in GCC community. Should we report the bug along with the suggested > patch at the same time? Or, after bug reporting we send the suggested > patch to gcc-patch@ and so on? Would a bug report be rejected because no > patch is present?
Dear Chang, I added the GCC list in CC in case others want to add something to my reply. Valid bug reports are not rejected because there is no patch. We could close a lot of bugs if we started doing that! But it wouldn't be a nice thing to do... Patches already tested should go to gcc-patches always. Bug reports sometimes contain patches because they are untested or incomplete, but they are posted to gcc-patches even if they don't require a review. If you propose a non-trivial patch, then GCC requires some legal papers to accept your code. See: http://gcc.gnu.org/contribute.html Trivial patches can go without copyright disclaimer/assignment, but you still need to test them and format them appropriately. Getting this wrong the first time is normal, so reviewers may ask you to do some formatting changes before accepting the patch. If you have more questions, please feel free to ask. Reading what people are doing in gcc-patches is also a good way to learn the right work-flow. Cheers, Manuel. > Thanks > -Chang > >
