This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
- From: Mike Stump <mikestump at comcast dot net>
- To: Chen Gang S <gang dot chen at sunrus dot com dot cn>
- Cc: Jeff Law <law at redhat dot com>, gcc-patches List <gcc-patches at gcc dot gnu dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Wed, 21 Jan 2015 10:46:55 -0800
- Subject: Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
- Authentication-results: sourceware.org; auth=none
- References: <54A0D2CA dot 3010806 at sunrus dot com dot cn> <54AAEF0E dot 6040706 at redhat dot com> <54BF776C dot 1090504 at sunrus dot com dot cn>
On Jan 21, 2015, at 1:54 AM, Chen Gang S <gang.chen@sunrus.com.cn> wrote:
> On 1/6/15 04:07, Jeff Law wrote:
>>
>>> * toplev.c (init_local_tick): Process the failure when read
>>> fails for random_seed.
>> This is fine for the trunk. Please install.
> I am not familiar with the related working flow, who should
> install this patch?
Anyone with write privileges can do this. You can request installation of the patch with the magic phrase:
I don’t have write access yet nor is my paperwork compete, can someone install this for me?
This will prompt a volunteer to step forward and help get it installed. When they are done, they will say, installed, close any related bug report and if they are nice, tell you the commit number for the work. You can then update your tree, build and test and ensure the work is as you wanted it. Once it hits the trunk, you’re done. If the patch is important enough for a back-port, you can ask people to consider a back port, once the work has been proven on the trunk for a week or two.