This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: What is the proper protocol for submitting a bug report with a patch for a gcc V7 prerelease?
- From: Mikhail Maltsev <maltsevm at gmail dot com>
- To: David Gressett <DGressett at amli-denton dot com>, gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Mon, 1 May 2017 05:13:27 +0300
- Subject: Re: What is the proper protocol for submitting a bug report with a patch for a gcc V7 prerelease?
- Authentication-results: sourceware.org; auth=none
- References: <ABCD305D3C42374DA91D18ECDE128000032558262987@APPA-DC-S02.AMLI-DENTON.COM> <CAOqAUTgtnt18BgJPC2NzcisJS-Aer6mu-XgqBmmTA0PqfG=QGQ@mail.gmail.com>
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@gmail.com> wrote:
> On Mon, May 1, 2017 at 3:32 AM, David Gressett
> <DGressett@amli-denton.com> 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@gcc.gnu.org.
>
> 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@gcc.gnu.org.
> Since your patch is intended for GCC 7, you will need an approve from
> one of the release managers: Jakub Jelinek (jakub@redhat.com), Richard
> Biener (rguenther@suse.de), Joseph Myers (joseph@codesourcery.com).
> Add them to CC.
>
> --
> Regards,
> Mikhail Maltsev
--
Regards,
Mikhail Maltsev