This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] toplev.c: Process the failure when read fails for random_seed

From: Jeff Law <law at redhat dot com>
To: Chen Gang S <gang dot chen at sunrus dot com dot cn>
Cc: Mike Stump <mikestump at comcast dot net>, gcc-patches List <gcc-patches at gcc dot gnu dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
Date: Mon, 26 Jan 2015 14:56:54 -0700
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> <8808FAA9-0A81-47E4-8456-33F0F506AE25 at comcast dot net> <54C0E54F dot 4060702 at sunrus dot com dot cn> <54C1281F dot 1070000 at redhat dot com> <54C152BA dot 6010503 at sunrus dot com dot cn> <54C15520 dot 80703 at redhat dot com> <54C1628C dot 7070006 at sunrus dot com dot cn>

On 01/22/15 13:50, Chen Gang S wrote:

On 01/23/2015 03:53 AM, Jeff Law wrote:

On 01/22/15 12:42, Chen Gang S wrote:



Thank you very much for your help applying the 3 patches. :-)

No problem.


After finish the assignment working flow, I guess, I may have the write
access, then can finish these kinds of trivial patches by myself (will
not always bother other members any more).

Exactly.  They'll still need review/approval, but once approved, you'll be able to commit them yourself.


OK, thanks. I guess that is "Write After Approval" maintainer role.

And I want to consult: for passing assignment working flow, must I make
a patch which contents much code lines? (At present, my patches are all
trivial patch).

If really need a patch which contents enough code lines, please let me
know, and I shall try.

You can get write-after-approval access regardless of the size andcomplexity of your patches.


Jeff

Follow-Ups:
- Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
  - From: Chen Gang S

References:
- Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
  - From: Jeff Law
- Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
  - From: Chen Gang S
- Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
  - From: Mike Stump
- Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
  - From: Chen Gang S
- Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
  - From: Jeff Law
- Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
  - From: Chen Gang S
- Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
  - From: Jeff Law
- Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
  - From: Chen Gang S

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]