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: Joseph Myers <joseph at codesourcery dot com>
- To: Chen Gang S <gang dot chen at sunrus dot com dot cn>
- Cc: gcc-patches List <gcc-patches at gcc dot gnu dot org>, Jeff Law <law at redhat dot com>, Bin.Cheng <amker dot cheng at gmail dot com>
- Date: Tue, 20 Jan 2015 02:11:27 +0000
- 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> <54A0D47C dot 5000302 at sunrus dot com dot cn> <alpine dot DEB dot 2 dot 10 dot 1412302225240 dot 17381 at digraph dot polyomino dot org dot uk> <54BD2824 dot 8020200 at sunrus dot com dot cn>
On Mon, 19 Jan 2015, Chen Gang S wrote:
> On 12/31/2014 06:26 AM, Joseph Myers wrote:
> > On Mon, 29 Dec 2014, Chen Gang S wrote:
> >
> >> And in honest, this year what I have done is really not quite well, next
> >> year I should be improved: should scanning Bugzilla and try to fix the
> >> existing issues (just like another members' suggestions to me).
> >
> > Note that for any substantial patches you'll need to complete the
> > copyright assignment paperwork (I don't see you listed in copyright.list
> > at present).
> >
>
> Excuse me, I am not quite familiar with the related working flow, at
> present, I finished assignment paperwork for binutils and gdb, and I
> am one of write after approval member for binutils and gdb.
>
> Do you mean I need follow the same working flow for gcc, just as for the
> binutils and gdb? (or only post my assignment is OK?).
You need to complete the same assignment form. Start with
http://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future
but this time name GCC as the package.
--
Joseph S. Myers
joseph@codesourcery.com