Hi all,
I write this mail with great sadness, but I've recently been informed
that Ge Van Geldorp, one of the original and important contributers to
the ReactOS project has recently passed away.
Having met up with him personally, I can say with some confidence that
he was not only blessed with an impressive skill in the hobby /
industry we all love, but was also a man of great integrity.
Being one of my original mentors in reactos, and having spent time
busting our guts at various linux projects with him trying to convince
the unix fanatics of the merits of NT, I can assure you that this he
was both a great colleague and friend. I'm sure all the old school
reactos devs would more than agree.
I propose we have some sort of eulogy on our homepage. I'd be more
than willing to compose something.
If people would like to send their thoughts, wishes or memories, I'd
be more than happy to compile them.
Ged.
Hiya
Managed to find Greg brother's letter to Wine, with bit more details regarding this tragedy. Since GvG was also our man, not only Wine's, perhaps some collaborative effort could be set to commemorate him.
With best regards
Caemyr
-------- Original Message --------
Subject:
Date:
From:
To: RE: Ge van Geldorp
Thu, 9 Jun 2011 23:05:46 +0200
Erven Gé van Geldorp <erven.van.geldorp <at> gmail.com>
'Paul Vriens' <paul.vriens.wine <at> gmail.com>
Hi all,
My name is Arno van Geldorp. I’m the brother of Gé (Greg) van Geldorp. I’m very sorry that I have to inform you that Greg has passed away almost 3 weeks ago. 2 Months earlier he was diagnosed with cancer in a very aggressive form.
I know he made his contribution to the Wine project. And that one of them is the WineTestBot. His passing away went so fast that he didn’t have the time to inform me all about it. What he did ask me is to make sure that the server where the WineTestBot is running on will be hosted for at least 2 more years. So we will take care of that. But I don’t know if anyone took over the administration off the server.
If anyone took over the administration from Greg could you please contact me at erven.van.geldorp at gmail.com
Kind regards,
Arno van Geldorp
Am 09.06.2011 15:56, schrieb tkreuzer(a)svn.reactos.org:
> Author: tkreuzer
> Date: Thu Jun 9 13:56:44 2011
> New Revision: 52156
>
> URL: http://svn.reactos.org/svn/reactos?rev=52156&view=rev
> Log:
> [BOOTSECTOR]
> - export obj2bin on gcc builds, too
> - Add new macro CreateBootSectorTarget2, which uses portable assembly and use it with isoboot.S. I will replace all bootsectors with the new code one at a time, and in the end we can eventually drop nmake
> - add wrapper isobtrt.S, which defines ROS_REGTEST and includes isoboot.S
>
I mean of course "drop nasm" not "drop nmake"
The notification routine can change the list, as there is no lock involved.
Therefore, you should grab the next entry before notifying the driver, to maintain a consistent list state.
--
Best regards,
Alex Ionescu
On 2011-06-02, at 1:43 PM, pschweitzer(a)svn.reactos.org wrote:
> + DriverNotificationRoutine(DeviceObject, TRUE);
> +
> + /* Go to the next entry */
> + ListEntry = ListEntry->Flink;
Hiya
The today's failure of my slaves can be explained two-way.
First, buildslaves (windows ones especially, but not only) seem to be very vulnerable to ping dropouts. A single icmp drop is resulting in build interruption.
Second, the hetzner.de hosting is dropping packets from my provider (atman.pl) all the way from teleport to reactos host, at a rate of one every few minutes or even more.
Combined those two, any build started at the moment is dropped after 2-3 minutes of runtime.
I have no idea if the network issue is temporary or not, thus no chance to predict when we will continue with runtime, Any ideas?
With best regards
Caemyr