Re: What is the proper protocol for submitting a bug report with a patch for a gcc V7 prerelease?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Oops, I should have sent this message to the gcc-help mailing list too.

On Mon, May 1, 2017 at 5:10 AM, Mikhail Maltsev <maltsevm@xxxxxxxxx> wrote:
> On Mon, May 1, 2017 at 3:32 AM, David Gressett
> <DGressett@xxxxxxxxxxxxxxx> wrote:
>> The subject line says it all. It has been a while since I submitted
>> a gcc bug report and patch, and the last one was not used because I did something wrong.
> Bugs should be reported to the GCC bugzilla: https://gcc.gnu.org/bugzilla
> Unfortunately, there is a warning in bugzilla, which says "User
> account creation filtered due to spam.". So, if you don't have an
> account you'll probably need to register it manually by writing an
> email to overseers@xxxxxxxxxxx.
>
> As for the patch, there is a contributor's guide here:
> https://gcc.gnu.org/wiki/GettingStarted
> You should test your patch and post it to gcc-patches@xxxxxxxxxxx.
> Since your patch is intended for GCC 7, you will need an approve from
> one of the release managers: Jakub Jelinek (jakub@xxxxxxxxxx), Richard
> Biener (rguenther@xxxxxxx), Joseph Myers (joseph@xxxxxxxxxxxxxxxx).
> Add them to CC.
>
> --
> Regards,
>    Mikhail Maltsev

-- 
Regards,
   Mikhail Maltsev



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux