victor martinez | 18 May 11:48 2015
Picon

ReactOS Updates flowing to our Social Channels.

Hi guys!

After a week dealing with several scripts and options, we're finally integrating the most important info from Reactos.org and Community.reactos.org directly to our Social channels to keep a constant flow of updates to our followers.

Since now our ReactOS Facebook and ReactOS Twitter will be automatically updated when...
... A Jira bugreport is resolved with a 'Fixed' and 'Cannot reproduce' status.
... A blog post is published in "ReactOS.org"
... A blog post is published in "Community.ReactOS.org"

Some of the features:
- Updates are queued and published with a time gap between them, so in case, eg, a Tester/Dev runs a Spring Cleanup, we won't be publishing 10 Jira reports in the same minute.
- Facebook and Twitter updates include pictures in case the blog post or the Jira report has one. So please add a picture in case you're blogging even if it is just a screenshot of you running "whatever" in ReactOS.
- Includes #hashtags related to the current Jira/Blog report.
- Uses bit.ly shortener when needed.
- And several hidden Easter Eggs in Twitter...(I was bored in the train)

If you've any suggestions about other potential updates to be sent to our Social Channels, just tell me and I'd try to integrate them in an automated way.

I'm planning a way to ease and have community contributions filtered and joining the automated flow, but it'll have to wait until I master Drupal. Also I'm working in some "crossposting" among our Social Channels, so a direct post in Facebook not coming from our PR Update System is replicated in Twitter and the other way around.

We can be really proud of the current PR Update system implemented, since probably it even beats several bigger opensource projects and/or companies out there.

If you didn't join our Twitter or Facebook yet, please feel free to join:
- Facebook: https://www.facebook.com/pages/ReactOS/19143619259
- Twitter: http://www.twitter.com/reactos

Brought to you by the ReactOS PR Team.




_______________________________________________
Ros-dev mailing list
Ros-dev@...
http://www.reactos.org/mailman/listinfo/ros-dev
Timo Kreuzer | 17 May 10:41 2015
Picon

Name of builders/testers in buildbot

Hi,

The names for our builders / testers don't seem to be optimal to me. And 
since they seem to be sorted in the waterfall display alphabetically 
now, I suggest renaming them in the following way:
Build_GCCLin_Debug
Build_GCCLin_Release
Build_GCCWin
Build_MSVC_x64
Build_MSVC_x86
Test_KVM
Test_VBox
Test_VMW
Test_VMW_Hybrid
Test_WHS

This way it is much more consistent, limited to actually useful 
information and would sort them nicely with builders left and testers right.

Regards,
Timo

Attachment (smime.p7s): application/pkcs7-signature, 4980 bytes
_______________________________________________
Ros-dev mailing list
Ros-dev@...
http://www.reactos.org/mailman/listinfo/ros-dev
Thomas Faber | 16 May 15:29 2015

Re: [ros-diffs] [tkreuzer] 67718: [CRT] Add simple C implementations for acosf, ceilf, floorf, fmodf and fix sqrtf

On 2015-05-14 15:44, tkreuzer@... wrote:
> +_Check_return_
> +float
> +__cdecl
> +ceilf(
> +_In_  float x)
> +{
> +    return (float)ceilf((double)x);
> +}

> +_Check_return_
> +float
> +__cdecl
> +floorf(
> +_In_  float x)
> +{
> +    return (float)floorf((double)x);
> +}

Did you mean to call ceil/floor here?
Thomas Faber | 14 May 14:50 2015

Re: [ros-diffs] [tkreuzer] 67709: [D3DX9_36/WINED3D] - Remove useless copysignf invocation and the wrong defines for it - BrokenHacksOnTopOfBrokenCode--; - Should be sent upstream

On 2015-05-14 06:00, tkreuzer@... wrote:
> -    int sign = (copysignf(1, in) < 0);
> +    int sign = (in < 0);

> -    if (copysignf(1.0f, value) < 0.0f)
> +    if (value < 0.0f)
>           ++idx;

I believe the behavior would be different here for negative zero:
copysignf(1.0f, -0.0f) should be < 0.0f
-0.0f should be == 0.0f

Maybe that's the reason for having these calls?
Timo Kreuzer | 13 May 02:10 2015
Picon

Re: [ros-diffs] [akhaldi] 67689: [CMAKE] The /SUBSYSTEM flag takes uppercase parameters.

Can you please also add an approproate value for ARM (I guess win8)? :)

Am 12.05.2015 um 14:18 schrieb akhaldi@...:
> Author: akhaldi
> Date: Tue May 12 12:18:02 2015
> New Revision: 67689
>
> URL: http://svn.reactos.org/svn/reactos?rev=67689&view=rev
> Log:
> [CMAKE] The /SUBSYSTEM flag takes uppercase parameters.
>
> Modified:
>      trunk/reactos/cmake/msvc.cmake
>
> Modified: trunk/reactos/cmake/msvc.cmake
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/cmake/msvc.cmake?rev=67689&r1=67688&r2=67689&view=diff
> ==============================================================================
> --- trunk/reactos/cmake/msvc.cmake	[iso-8859-1] (original)
> +++ trunk/reactos/cmake/msvc.cmake	[iso-8859-1] Tue May 12 12:18:02 2015
>  <at>  <at>  -210,10 +210,11  <at>  <at> 
>   endfunction()
>   
>   function(set_subsystem MODULE SUBSYSTEM)
> +    string(TOUPPER ${SUBSYSTEM} _subsystem)
>       if(ARCH STREQUAL "amd64")
> -        add_target_link_flags(${MODULE} "/SUBSYSTEM:${SUBSYSTEM},5.02")
> -    else()
> -        add_target_link_flags(${MODULE} "/SUBSYSTEM:${SUBSYSTEM},5.01")
> +        add_target_link_flags(${MODULE} "/SUBSYSTEM:${_subsystem},5.02")
> +    else()
> +        add_target_link_flags(${MODULE} "/SUBSYSTEM:${_subsystem},5.01")
>       endif()
>   endfunction()
>   
>
>
>

Attachment (smime.p7s): application/pkcs7-signature, 4980 bytes
_______________________________________________
Ros-dev mailing list
Ros-dev@...
http://www.reactos.org/mailman/listinfo/ros-dev
Thomas Faber | 12 May 14:33 2015

Re: [ros-diffs] [akhaldi] 67683: [SHELL32] Don't provide the format option when the volume is read only. By Barrett Karish. CORE-9530

On 2015-05-12 06:57, akhaldi@... wrote:
> +/* FIXME: ntifs.h */
> +#define FILE_READ_ONLY_VOLUME 0x00080000

This should go in ndk/iotypes.h inside an NTOS_MODE_USER ifdef.
Pierre Schweitzer | 10 May 19:43 2015

Re: [ros-builds] Trunk_x86_GCCLin Release: build failed

Manually uploaded.

On 10/05/2015 19:28, buildbot@... wrote:
> The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Release while building ReactOS.
> Full details are available at:
>  https://build.reactos.org/builders/Trunk_x86_GCCLin%20Release/builds/1177
> 
> Buildbot URL: https://build.reactos.org/
> 
> Buildslave for this Build: Debug
> 
> Build Reason: The Periodic scheduler named 'Release' triggered this build
> Build Source Stamp: HEAD
> Blamelist: 
> 
> BUILD FAILED: failed shell
> 
> sincerely,
>  -The Buildbot
> 
> 
> 
> 
> 

--

-- 
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.

Attachment (smime.p7s): application/pkcs7-signature, 5328 bytes
_______________________________________________
Ros-dev mailing list
Ros-dev@...
http://www.reactos.org/mailman/listinfo/ros-dev
James Tabor | 8 May 02:58 2015
Picon

[ros-diffs] [hbelusca] 67595: [NTVDM] - Move some interrupt initialization where it belongs and activate few other ones. - Initialize interruct vector for INT 2Ah (Network check) because some apps directly cal...

_______________________________________________
Ros-dev mailing list
Ros-dev@...
http://www.reactos.org/mailman/listinfo/ros-dev
victor martinez | 7 May 14:17 2015
Picon

#ReactOS in OpenExpo'15 (Madrid) and other PR stuff

Hi guys!
I'm proud to confirm that ReactOS project will be shown in OpenExpo'15 in Madrid, 16th June.
OpenExpo is one of the greatest open source events in Spain: http://www.openexpo.es
We'll have the opportunity to give a Talk plus some Hacking lab (wish me good luck!). 
If anyone wants to come, I've one additional free pass.

On the other hand, the open source 2/OS project is pushing forward through some Latam guys:
Seems they're using ReactOS code in their project according with their tweets:
(Translation: We're using code of reactos.org and winehq.org, we have had to interact with networking stack with ROS using JAVA)
Using Java???

And they seemed to have some issues with ReactOS code:

Keep rockin'!

_______________________________________________
Ros-dev mailing list
Ros-dev@...
http://www.reactos.org/mailman/listinfo/ros-dev
stack exchange | 6 May 18:34 2015
Picon
Picon

Debug output

Whats the difference between DPRINT and DbgPrint? I wrote a little 
program that I can use to observe pipes, which I use for debugging. The 
text from DPRINT is there, but where does DbgPrint go and why are there 
multiple different debugging aids?
Ged Murphy | 5 May 21:41 2015
Picon

Re: [ros-diffs] [gedmurphy] 67563: [DDK] Fix the FS filter callback definitions

Well this is a weird one, the DDK says these callbacks are cdecl (missing NTAPI) and anyone building against
the DDK will obviously declare their callbacks to match this convention.  However internally, windows
uses stdcall for these callbacks.

I can't find much by way of problems people have encountered with this, so why aren't people seeing problems
with the way the stack is cleaned up? Anyone have any ideas before I blindly revert this change?

Ged.

-----Original Message-----
From: Ros-diffs [mailto:ros-diffs-bounces@...] On Behalf Of gedmurphy@...
Sent: 05 May 2015 19:54
To: ros-diffs@...
Subject: [ros-diffs] [gedmurphy] 67563: [DDK] Fix the FS filter callback definitions

Author: gedmurphy
Date: Tue May  5 18:54:28 2015
New Revision: 67563

URL: http://svn.reactos.org/svn/reactos?rev=67563&view=rev
Log:
[DDK]
Fix the FS filter callback definitions

Modified:
    trunk/reactos/include/ddk/ntifs.h

Modified: trunk/reactos/include/ddk/ntifs.h
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/include/ddk/ntifs.h?rev=67563&r1=67562&r2=67563&view=diff
==============================================================================
--- trunk/reactos/include/ddk/ntifs.h	[iso-8859-1] (original)
+++ trunk/reactos/include/ddk/ntifs.h	[iso-8859-1] Tue May  5 18:54:28 2015
 <at>  <at>  -4890,12 +4890,12  <at>  <at> 
 } FS_FILTER_CALLBACK_DATA, *PFS_FILTER_CALLBACK_DATA;

 typedef NTSTATUS
-(NTAPI *PFS_FILTER_CALLBACK) (
+(*PFS_FILTER_CALLBACK) (
   _In_ PFS_FILTER_CALLBACK_DATA Data,
   _Out_ PVOID *CompletionContext);

 typedef VOID
-(NTAPI *PFS_FILTER_COMPLETION_CALLBACK) (
+(*PFS_FILTER_COMPLETION_CALLBACK) (
   _In_ PFS_FILTER_CALLBACK_DATA Data,
   _In_ NTSTATUS OperationStatus,
   _In_ PVOID CompletionContext);

Gmane