On 1/27/15 05:56, Jeff Law wrote:
> 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 worki
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 the
On 1/26/15 03:50, Gerald Pfeifer wrote:
> On Friday 2015-01-23 04:50, Chen Gang S wrote:
>> 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).
>
> No, the assignment process does no
On Friday 2015-01-23 04:50, Chen Gang S wrote:
> 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).
No, the assignment process does not have any requirements on
past or current patche
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 pat
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
On 01/23/2015 12:41 AM, Jeff Law wrote:
> On 01/22/15 04:55, Chen Gang S wrote:
>> On 01/22/2015 02:46 AM, Mike Stump wrote:
>>> On Jan 21, 2015, at 1:54 AM, Chen Gang S wrote:
On 1/6/15 04:07, Jeff Law wrote:
>
>> * toplev.c (init_local_tick): Process the failure when read
>>
On 01/22/15 04:55, Chen Gang S wrote:
On 01/22/2015 02:46 AM, Mike Stump wrote:
On Jan 21, 2015, at 1:54 AM, Chen Gang S 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 in
On 01/22/2015 02:46 AM, Mike Stump wrote:
> On Jan 21, 2015, at 1:54 AM, Chen Gang S 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 fam
On Jan 21, 2015, at 1:54 AM, Chen Gang S 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
> i
On 1/6/15 04:07, Jeff Law wrote:
> On 12/28/14 21:04, Chen Gang S wrote:
>> When failure occurs, random_seed may not be 0, so need reset it to 0
>> manually, or will let the next call init_random_seed() incorrect. The
>> related warning:
>>
>>g++ -c -DTARGET_NAME=\"parisc-gchen-linux\" -g -O2
On 1/20/15 10:11, Joseph Myers wrote:
> 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 scan
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
> >> exis
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 t
On 1/6/15 04:07, Jeff Law wrote:
> On 12/28/14 21:04, Chen Gang S wrote:
>> When failure occurs, random_seed may not be 0, so need reset it to 0
>> manually, or will let the next call init_random_seed() incorrect. The
>> related warning:
>>
>>g++ -c -DTARGET_NAME=\"parisc-gchen-linux\" -g -O2
On 12/28/14 21:04, Chen Gang S wrote:
When failure occurs, random_seed may not be 0, so need reset it to 0
manually, or will let the next call init_random_seed() incorrect. The
related warning:
g++ -c -DTARGET_NAME=\"parisc-gchen-linux\" -g -O2 -DIN_GCC
-DCROSS_DIRECTORY_STRUCTURE -fno-e
On 12/31/14 06:26, 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)
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'l
On Mon, 29 Dec 2014, Chen Gang S wrote:
> 2014-12-27 Chen Gang
>
> * toplev.c (init_local_tick): Process the failure when read
> fails for random_seed.
OK.
--
Joseph S. Myers
jos...@codesourcery.com
Excuse me, I have to send mail use my other mail address.
During these days, gmail is broken in China, except Safari from Mac Book,
none of my email client can connect to gmail (even Safari from iPad, can
not connect gmail).
And in honest, this year what I have done is really not quite well, next
se (fd);
}
--
1.9.3 (Apple Git-50)
From 05faeede37f6e383f69a1398d355ea8ce3687583 Mon Sep 17 00:00:00 2001
From: Chen Gang
Date: Sat, 27 Dec 2014 15:55:57 +0800
Subject: [PATCH] toplev.c: Process the failure when read fails for random_seed
When failure occurs, random_seed may not be 0, so nee
21 matches
Mail list logo
