Hi, I will have to take down the Fezile server for a short period of time in about 2 weeks due to a move of the server room to a fireproof, fairly burglarproof security room (brickswork with steeldoor, no windows). However, it is beeing remodelled right now, and then the aircondition, ethernet lines and power is going to be installed, so I guess two weeks.
I have some computers to move so the power down may take some time, but I will try to make the move as fast as possible.
During this time I will try to prepare for a ReactOS LAN behind the Fezile server on the second and third LAN adapter, for example for build testing on real hardware or another build bot.
Yours sincerely,
Jaix Bly (Jan Blomqvist Kinander)
Hello,
I want to remind you of the monthly status meeting taking place today, Thursday the 26th of May at 20:00 UTC at freenode #reactos-meeting.
The suggested (subject to change and addition before meeting starts) meeting agenda is:
- Status of our GSoC participation
- Current ReactOS work. Developers reporting their status.
Those who don’t attend will be able to read up the meeting minutes later.
See you at the meeting today!
WBR,
Aleksey Bragin.
Hiya
Our nightly builds repository is not working and people cannot download
anything from it. Is it a known issue? Any idea when it might be fixed?
Best regards
Commit messages should include the component name that your commit changes.
Messages like the following:
[nyadav] 51882: Fix a Deadlock (nyadav(a)svn.reactos.org)
will result in me coming after you when I need to do the changelog for the
next release. Messages should be formatted like this:
[tkreuzer] 51885: [WIN32K] - Fix the bitmap alignment issue that caused
broken scrollbar pattern (tkreuzer(a)svn.reactos.org)
Z98
Hi,
it appears that Linux buildbot is running a bad issue and is looping on building. If anyone can have a look?
To prevent flood on IRC, I silent bot and removed voice.
Thanks in advance
That was very confusing :)
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of osiejka(a)svn.reactos.org
Sent: 23 May 2011 22:49
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [osiejka] 51874: [RPCSS] Addenum. This change slipped past in commit 51873. Fix name of irot header include, which should be irot.h and not irot_s.h. Fixes rpcss build in MSVC.
Author: osiejka
Date: Mon May 23 21:49:12 2011
New Revision: 51874
URL: http://svn.reactos.org/svn/reactos?rev=51874&view=rev
Log:
[RPCSS]
Addenum. This change slipped past in commit 51873. Fix name of irot header include, which should be irot.h and not irot_s.h. Fixes rpcss build in MSVC.
Modified:
trunk/reactos/base/services/rpcss/irotp.c
Modified: trunk/reactos/base/services/rpcss/irotp.c
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/base/services/rpcss/irotp.…
==============================================================================
--- trunk/reactos/base/services/rpcss/irotp.c [iso-8859-1] (original)
+++ trunk/reactos/base/services/rpcss/irotp.c [iso-8859-1] Mon May 23 21:49:12 2011
@@ -1,5 +1,5 @@
/*
- * Running Object Table
+ * Running Object Table
*
* Copyright 2007 Robert Shearman
*
It was spotted by MSVC build:
P:\Trunk_slave\MSVC-trunk\build\base\services\rpcss\irotp.c(28) : fatal
error C1083: Cannot open include file: 'irot_s.h': No such file or directory
LINK : fatal error LNK1104: cannot open file
'CMakeFiles/rpcss.dir/irotp.c.obj'
In base\services\rpcss\irotp.c:28 we see: #include "irot_s.h"
This file is not present in ReactOS trunk. In WINE's RPCSS
http://source.winehq.org/git/wine.git/blob/HEAD:/programs/rpcss/irotp.c :28
we have: #include "irot.h" which is also missing, and listed in .gitignore:
http://source.winehq.org/git/wine.git/blob?f=.gitignore
260 programs/rpcss/irot.h
261 programs/rpcss/irot_s.c
I think we can safely clean it up, perhaps adding proper line to ros-diff,
but i would like to ask you guys for confirmation.
Regards
Hi ros-dev,
I've seen shell32_new being added into trunk by r51768, but haven't heard of
anything else about it. From what I can see it changes shell32 from C to
C++, which looks like a good move.
Problematic seems to me that it is completely out of sync with trunk's
shell32 (judging from the translations alone).
It might also be annoying for merging future patches, since the C to C++
move changes the code substantially.
So are there any plans concering shell32_new? Do I have to merge all code
changes in C and C++ or is shell32(_old) going to be dumped anytime soon?
Best regards,
Gregor