Re: [ros-dev] [ros-diffs] [aandrejevic] 60485: [SOFT386] Change the license of Soft386 to GPLv2. The previous license was also GPLv2, but it had a runtime linking exception. The new license is the ori

No, LGPL allows link-time merging of non-LGPL object files with LGPL code, as long as you provide the object files necessary to reconstruct the binary after changing the LGPL code. On 2 October 2013 19:36, Colin Finck co...@reactos.org wrote: Aleksey Bragin alek...@reactos.org wrote: Please

Re: [ros-dev] Building and installing ReactOS on newer computer

You can find ready-to-use builds of recent SVN revisions at: https://www.reactos.org/getbuilds If you don't see builds for the latest, use the arrows to go back until you find one that has files. You can NOT install ReactOS on a USB hard drive, though. If you do want to build from source

Re: [ros-dev] [ros-diffs] [ekohl] 61145: [FASTFAT] FsdGetFsVolumeInformation: Return volume creation time.

The exact words of the license, as seen at http://www.ohloh.net/licenses/mslpl (I couldn't find a better link for it), are: 4. (F) Platform Limitation- The licenses granted in sections 2(A) 2(B) extend only to the software or derivative works that you create that run on a Microsoft Windows

Re: [ros-dev] [ros-diffs] [ekohl] 61145: [FASTFAT] FsdGetFsVolumeInformation: Return volume creation time.

, but it would require a more lawyer-y mind to figure out. On 29 November 2013 17:35, David Quintana (gigaherz) gigah...@gmail.com wrote: The exact words of the license, as seen at http://www.ohloh.net/licenses/mslpl (I couldn't find a better link for it), are: 4. (F) Platform Limitation

Re: [ros-dev] [ros-diffs] [ekohl] 61145: [FASTFAT] FsdGetFsVolumeInformation: Return volume creation time.

it's on Microsoft Windows. Then again, I'm not a lawyer either and I could be wrong too. It would be great if someone who knows a lot about licenses explained this. Regards, Alexander On Fri, Nov 29, 2013 at 05:35:21PM +0100, David Quintana (gigaherz) wrote: The exact words of the license

Re: [ros-dev] Does 'make install' work on 0.3.15?

. On 13 December 2013 10:25, Marvin Zhang fanzi2...@gmail.com wrote: Hi David, Do you mean you have to generate bootcd and install it again once if you just modify some modules? Marvin On Fri, Dec 13, 2013 at 5:18 PM, David Quintana (gigaherz) gigah...@gmail.com wrote: As far as I know

Re: [ros-dev] Installing and running ReactOS on modern hardware

First of all, I'm not an expert when it comes to what ReactOS supports in terms of real hardware. I believe (someone will correct me if I'm wrong), that ReactOS is not currently able to boot from USB, and in fact, will fail to boot at all if an incompatible USB controller (which is most of them,

Re: [ros-dev] Installing and running ReactOS on modern hardware

image over the network, but I don't think the process is usable quite yet (someone correct me if I'm wrong). On 25 March 2014 10:25, Thomas Mueller mueller6...@twc.com wrote: from David Quintana (gigaherz) gigah...@gmail.com: [-- Type: multipart/alternative, Encoding: 7bit, Size: 5.8K

Re: [ros-dev] Installing and running ReactOS on modern hardware

. (If anyone with more knowledge wants to take over the conversation...) On 26 March 2014 04:34, Thomas Mueller mueller6...@twc.com wrote: from David Quintana (gigaherz) gigah...@gmail.com: [-- Attachment #1 --] [-- Type: multipart/alternative, Encoding: 7bit, Size: 9.5K --] Content-Type

Re: [ros-dev] [ros-diffs] [dquintana] 63044: [RSHELL] [SHELL32] * Move the IID_NULL_PPV_ARG macro to the shobj_undoc header, next to the (also ros-specific) IID_PPV_ARG macro, so that it can be used e

There was a call to GetUIObjectOf for interface IExtractIconA, being assigned to a pointer of type IExtractIconW, I'm 100% sure of it, although I can't find the code in the diff.. :/ On 29 April 2014 13:47, Thomas Faber thomas.fa...@reactos.org wrote: On 2014-04-29 13:14,

Re: [ros-dev] libusb-win32 - can we use it?

As far as I understand, libusb is a means for usermode applications to attach themselves to an usb device, sending messages and receiving replies. What would the purpose be for libusb in the context of ReacOS? On 19 May 2014 12:38, Alexander Rechitskiy art1st...@yandex.ru wrote:

Re: [ros-dev] libusb-win32 - can we use it?

://www.reactos.org/forum/viewtopic.php?f=4t=13008p=106242#p106242 On Mon, May 19, 2014 at 5:56 AM, David Quintana (gigaherz) gigah...@gmail.com wrote: As far as I understand, libusb is a means for usermode applications to attach themselves to an usb device, sending messages and receiving replies

Re: [ros-dev] [ros-diffs] [hbelusca] 63599: [TASKMGR]: Use the EndTask API to kill tasks.

It's equivalent to writing something != 0, although less readable. I have no idea if compilers actually generate better code for it, or people just do it because it's shorter to type. On 16 June 2014 11:09, Ged Murphy gedmurphy.mailli...@gmail.com wrote: Yes, the double negate is a little

Re: [ros-dev] Claim your commits

This website is under heavy load -- Maybe later, if the site survives ;P On 7 October 2014 14:19, Alexander Rechitskiy art1st...@yandex.ru wrote: Dear ReactOS Developers Please join Black Duck Open Hub (ex ohloh) and claim your commits for ReactOS and other opensource projects.

Re: [ros-dev] Claim your commits

Nice to know my old ohloh account still works ;P I added myself: https://www.openhub.net/accounts/gigaherz/positions On 18 October 2014 23:51, Alexander Rechitskiy art1st...@yandex.ru wrote: it works now! 07.10.2014, 19:19, David Quintana (gigaherz) gigah...@gmail.com: This website is under

Re: [ros-dev] [ros-diffs] [akhaldi] 65249: [SHELL32] * bool = BOOL.

All the common COM interfaces use BOOL instead of bool, because it's more compiler-agnostic and it matches better the Win32 API type usage. If we use bool, we may risk a consumer of the interface using the wrong size for bool, so although ISFHelper is an internal interface not meant to be used by

Re: [ros-dev] ReactOS/Wine patches.

(I wrote this 3 hours ago but forgot to send) Hello, I'm not Sylvain, but I want to make a note regardless. Keep in mind that almost all the developers are contributors that work in their spare time. What you suggest is that those developers who donate their time for the project should also take

Re: [ros-dev] Replacing unsafe TRUE comparisons (Following Re: bool = BOOL)

To me it's a matter of readability/semantics. Even though a BOOL is still an integer, if a variable is clearly meant for the purpose of a bool, such as if (bEnableThis), then using != FALSE is redundant. If the variable doesn't have an implicit boolean-ness in its name, then it may be best to

Re: [ros-dev] Replacing unsafe TRUE comparisons (Following Re: bool = BOOL)

@Eric: Do a quick google search for TROOLEAN, and you'll know why your assumption that BOOL only has two possible values is wrong. On 16 November 2014 11:19, Eric Kohl eric.k...@t-online.de wrote: Hello Love, I think you are trying to fix a bug at the wrong end. The boolean types BOOL and

Re: [ros-dev] [ros-diffs] [dquintana] 65415: [SHELL32] * Commit the folder location fixes. They are mostly untested due to being unable to boot to desktop, but looking at the contents of the HDD after

I was on my phone and it replied to the wrong email (personal instead of mailing list), so I'll take this chance to expand the reply adding a little more detail. The code appears to work as far as I can tell, but I need to check the existing tests for it, and possibly add new ones. Then I think

Re: [ros-dev] Selling ReactOS CDs

The short answer to that is: Are we prepared to answer the demands of people who paid money to get ReactOS, and then discover not everything works? They paid money so they WILL feel entitled to have customer support for it. On 19 November 2014 13:50, Hermès BÉLUSCA - MAÏTO hermes.belu...@sfr.fr

Re: [ros-dev] Partition size and FAT32 cluster size?

Note that because flash drives tend to have larger sectors and specially much bigger erase groups, it's often more interesting to format flash drives as 16k rather than 4k, even if it can waste some space with small files. On 8 December 2014 at 03:48, Thomas Mueller mueller6...@twc.com wrote:

Re: [ros-dev] Installing ReactOS to a folder

Back in the days when we used the old rbuild build system, we did have a make install that did just what you describe, but the system was lost in the upgrade to cmake, and none of the current developers wants to reimplement it. If any of you want to try, it would be welcome by many. On 9 December

Re: [ros-dev] [ros-diffs] [pschweitzer] 65596: [NTOSKRNL] THE oneliner.... Properly read the information from the IRP to get the reparse tag. This fixes the handling of reparse mount points in ReactOS

You mean if it changes AFTER installation? Because I recall installing Windows XP on top of another Windows XP, and getting the OS drive to be mapped to D: and everything was working fine (just on the wrong drive). The problem was I had to reformat and install with a different media in order to

[ros-dev] Could someone take over CORE-7864?

Link, for ease of access: https://jira.reactos.org/browse/CORE-7864 The bug was assigned to me a while ago, but this seems to be primarily win32k issues, which are outside my area of expertise. Someone else may be able to handle it better. ___ Ros-dev

Re: [ros-dev] ReactOS versioning

SxS doesn't require links, it makes use of them to reduce the actual disk usage. The conversation was about how many people hate the WinSxS folder because when you look at the properties in explorer it shows a very large number of GB, but fail to realize this number is not accurate due to the

Re: [ros-dev] ReactOS versioning

Hmm I may be completely mistaken but doesn''t Windows use the ActCtx stuff for compatibility profiles? Wouldn't we be able to use forward-compatibility profiles? If that's right, it may be the cleanest system for it. On 7 March 2015 at 22:38, Jerome Gardou jerome.gar...@reactos.org wrote: Le

Re: [ros-dev] [ros-diffs] [tkreuzer] 65893: [GDI32] Import metafile code from wine. The wine code is unmodified (please keep it that way) and used through a wrapper function dispatcher and some helper

Whoops I replied and THEN read the last line above... Nevermind this email. On 1 April 2015 at 00:29, David Quintana (gigaherz) gigah...@gmail.com wrote: Maybe we should send those fixes to wine-staging instead of actual wine? On 31 March 2015 at 22:39, Timo Kreuzer timo.kreu...@web.de wrote

Re: [ros-dev] [ros-diffs] [tkreuzer] 65893: [GDI32] Import metafile code from wine. The wine code is unmodified (please keep it that way) and used through a wrapper function dispatcher and some helper

Maybe we should send those fixes to wine-staging instead of actual wine? On 31 March 2015 at 22:39, Timo Kreuzer timo.kreu...@web.de wrote: Am 31.03.2015 um 21:11 schrieb Thomas Faber: Hey Timo, I was just about to sync enhmetafile.c with Wine and found that your original import had the

Re: [ros-dev] Intel Edison + ReactOS

Nice :D On 5 March 2015 at 18:13, Aleksey Bragin alek...@reactos.org wrote: Hi! I visited Intel's office in Moscow this week where I was given the brand new Intel Edison along with the Arduino-compatible prototype board. This story started by Alexander Rechitsky who brought all this to my

Re: [ros-dev] GSoC :: application rejected

There is no need to believe that Google hates us. As a company, they must have a preference: any project that may benefit their business, is a better choice than a project that doesn't affect them or affects them negatively. As ReactOS is right now, we are still very easily ignorable. A toy and

Re: [ros-dev] Setup on an extended partition

Upload the patch to JIRA, create a new issue entry if none exists for this. It's the preferred way to contribute to the project. People only get write access after they have proved themselves with writing patches, and the team trusts them to have some minimal quality and behaviour standards. ;P

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

Judging by the involved macro, if -0.0 is not 0, then the old code had exactly the same bug. On 14 May 2015 at 14:50, Thomas Faber thomas.fa...@reactos.org wrote: On 2015-05-14 06:00, tkreu...@svn.reactos.org wrote: -int sign = (copysignf(1, in) 0); +int sign = (in 0); -if

Re: [ros-dev] [ros-diffs] [dquintana] 67976: [DEVMGMT_NEW] At the request of Christoph von Wittich, bring devmgmt_new into the build. * Created CMakeLists.txt and added to parent folder. * Removed som

Oops, sorry about that. Christoph asked so I didn't think to consider if you were still working on it. On 31 May 2015 at 13:16, Ged Murphy gedmurphy.mailli...@gmail.com wrote: Eeek, I was working on this via VS and have quite a few changes in my WC, including CAtlString support for our ATL

Re: [ros-dev] Visual Studio Support

I don't get any error locally, it may be that your build folder became corrupted. It happens every now and then, that a file is out of date, but the build system doesn't realize it. Unless you mean building from INSIDE visual studio... that's not currently a supported build method, I believe. You

Re: [ros-dev] Visual Studio Support

Oh and by the way, you CAN use ninja with msvc compiler, too. I got the impression you assumed ninja=mingw, but if you do configure from a vs command prompt, it will default to ninja+msvc, which is what I mentioned as the fastest way to compile. On 6 August 2015 at 23:50, David Quintana (gigaherz

Re: [ros-dev] Visual Studio Support

: I mean build inside vs. It would be very great. But I have no problem building with mingw. Ah never know that msbuild work. Thanks for the response! 2015-08-06 23:21 GMT+02:00 David Quintana (gigaherz) gigah...@gmail.com: I don't get any error locally, it may be that your build folder

Re: [ros-dev] Visual Studio Support

using the configure script. As I see allmost all of the linking the problem comes from the functions that are implemented in assembly. Don't know. 2015-08-06 23:50 GMT+02:00 David Quintana (gigaherz) gigah...@gmail.com: In theory, yes, but in practice not everything required is built

Re: [ros-dev] [ros-diffs] [dreimer] 68645: [shell32] Change Trash to Recycle Bin by Lee Schroeder CORE-8391 #resolve #comment Committed the big one with changes to all RC files, because it's the right

I say this as a joke, but it also happens to be a perfectly valid argument in favour of the change: Calling it recycle bin promotes recycling, which is a good practice that the project should support, and well, you ARE recycling those HDD sectors for later use... ;P On 9 August 2015 at 12:32, Huw

Re: [ros-dev] Audio development

For COM classes in the context of ReactOS, I'd recomment the existing code in Shell components. for declaring and using COM classes from C, there's code coming from WINE that could serve as an example, and for proper COM done with C++, we have examples of both ATL-based COM such as the rshell

Re: [ros-dev] Visual Studio Support

is better build with mingw. 2015-08-07 0:10 GMT+02:00 David Quintana (gigaherz) gigah...@gmail.com: Would you want to pop into our IRC channel so we can troubleshoot in realtime? On 6 August 2015 at 23:56, Alberto Vaudagna alberto.vauda...@gmail.com wrote: ya the host files compile fine

Re: [ros-dev] Unify system icons into one central folder

Yes, it is indeed a ridiculous analogy. I believe there are too many advantages to have a unified place to have most of the common icons usable by any app that needs them. Note that my idea was for common icons, thing such the usual objects (document icon, folder icon, the configuration cogs,

Re: [ros-dev] Files in press-media repository

ov 1, 2015 at 1:49 PM, David Quintana (gigaherz) > <gigah...@gmail.com> wrote: >> >> JPEG is lossy. It's bad to store the original images in JPEG, for any >> purpose. >> >> You want to keep as much information as possible, which means >> something like R

Re: [ros-dev] [ros-diffs] [gedmurphy] 69650: The c++ bool is 1 byte, not 4. Thanks Thomas

The common computers never work with bits in memory. All the common operations work at LEAST in bytes, and often in larger units, so working with bits requires extra logic. Booleans are most commonly stored as 1 byte because of that. It is possible that come machines do use 1 bit, but they would

Re: [ros-dev] [ros-diffs] [hbelusca] 71524: [SHELL32] - Minor stylistic whitespace changes. - Use 'IDA_DESKBROWSER' instead of hardcoding its value. - The shell progman window uses the COLOR_DESKTOP a

This change sounds wrong to me too. On 5 June 2016 at 08:26, Thomas Faber wrote: > On 2016-06-05 01:29, hbelu...@svn.reactos.org wrote: > > -rcDesk.left = GetSystemMetrics(SM_XVIRTUALSCREEN); > > -rcDesk.top = GetSystemMetrics(SM_YVIRTUALSCREEN); > > -

Re: [ros-dev] [ros-diffs] [hbelusca] 71524: [SHELL32] - Minor stylistic whitespace changes. - Use 'IDA_DESKBROWSER' instead of hardcoding its value. - The shell progman window uses the COLOR_DESKTOP a

Went ahead and fixed it (r71526). On 5 June 2016 at 10:38, David Quintana (gigaherz) <gigah...@gmail.com> wrote: > Ah I see: it's misusing the rect. > > It later passes right+bottom as "cx" and "cy" to CreateWindowEx. I propose > getting rid of this rect

Re: [ros-dev] [ros-diffs] [mjansen] 71439: [APPHELP] Begin shimlib implementation. CORE-11329 Implement some macro's and functions that help when registering shims. These are all written in C, so that

Wine doesn't wrap C++, they just simply don't allow C in their codebase, period. It's annoying. On 31 May 2016 at 11:32, Ged Murphy wrote: > Would it not be better to do all this in C++ and let wine write a C > interface around it? > When we're trying to move to

Re: [ros-dev] [ros-diffs] [mjansen] 71439: [APPHELP] Begin shimlib implementation. CORE-11329 Implement some macro's and functions that help when registering shims. These are all written in C, so that

Gorden <drakekaizer...@gmail.com> wrote: > Question actually still stands though. If wine is not inclined to use our > code just because it's in C++, should that stop us from using it? We > already basically split with shell32. > > On Tue, May 31, 2016 at 4:45 AM, Dav

Re: [ros-dev] Error trying to checkout reactos sources

Can you try svn://svn.reactos.org/svn/reactos/trunk/ ? On 24 February 2016 at 17:11, Thomas Schweikle wrote: > Hi! > > trying to checkout reactos sources using svn leads to: > $ LANG=CC svn co https://svn.reactos.org/svn/reactos/trunk/reactos/ > reactos > svn: warning:

Re: [ros-dev] Error trying to checkout reactos sources

oops sorry it's svn://svn.reactos.org/reactos/trunk/ -- no /svn/ On 24 February 2016 at 17:31, David Quintana (gigaherz) <gigah...@gmail.com> wrote: > Can you try svn://svn.reactos.org/svn/reactos/trunk/ ? > > On 24 February 2016 at 17:11, Thomas Schweikle <tschwei...@gmail.com

Re: [ros-dev] Consideration for migrating from Subversion to Git

Sorry about that. I guess I have read a lot of technical papers ;P On 25 February 2016 at 12:47, Ged Murphy wrote: > Okay ignore me, we cleared it up in IRC. David means significant, I've > just never heard nevermind .. > > If moving to git will

Re: [ros-dev] Consideration for migrating from Subversion to Git

I think the real goal with moving to a platform such as github is reducing the entry barriers for new contributors. As it has been mentioned already, almost all projects who moved from SVN with "send patches" contribution system, to Git/Hg with Pull Requests have got non-negligible growth in

Re: [ros-dev] GSoC 2016: SSH Service

Out website's registration system was turned off while waiting for a solution to a spambot issue plaguing the services. You can request an account and one of our people will take care of it for you. You can join us on our IRC channel #reactos at freenode. On 19 March 2016 at 21:51, Михаил

Re: [ros-dev] ReactOS kernel driver

You should be coding the drivers so that they work on NT5.2/Windows Server 2003. Then, if the resulting driver does not work in ReactOS, it often means we have a bug in ReactOS itself. As for compiling with DDK/RosBE, I don't have much experience with drivers, but so far as I know, you'll

Re: [ros-dev] livecd and bootcd not working with VMware Workstation / ESX-Server

I know accounts are closed, that's why I said "normally", and continued the conversation by giving a possible temporary solution. On 3 March 2016 at 16:22, Thomas Schweikle wrote: > I've tried to report to jira, but I can't login with my old account > nor register.

Re: [ros-dev] livecd and bootcd not working with VMware Workstation / ESX-Server

Hello, we normally ask that bug reports be opened on our JIRA at https://jira.reactos.org/ Some months ago I had an issue with VMware, where boot would fail if I upgraded the VM to hardware version 11 or 12, and I had to set it to hardware version 10 for it to work correctly. I thoguht that issue

Re: [ros-dev] 502 Bad Gateway

Yes. Server issue. We all get it. On 28 March 2016 at 03:15, Javier Agustìn Fernàndez Arroyo wrote: > Hello, > > I am receiving this when trying to access website... > > Is anyone having the same problem? > > ___ > Ros-dev mailing

Re: [ros-dev] Greetings from GSoC student!

Welcome :) On 25 April 2016 at 16:27, mvardan wrote: > Hello ReactOS community! > > My name is Vardan. > > First of all I want to say thank you to all the members of this community > who helped me to figure out status of works and make a proposal for GSoC. > Also I want

Re: [ros-dev] Pale Moon drops ReactOS support

People need to stop worrying about "jumping in" on this conversation -- it's being discussed on the public mailing list because the opinion of the community DOES MATTER. so feel free to provide any and all input you think is relevant. On 19 May 2016 at 00:28, Dimitrij Klingbeil

Re: [ros-dev] 4th scenario

No one is suggesting paging the kernel. Stop being paranoid about that. We are speaking about API interfaces for user apps and drivers. Whatever that implies, will be examined on a case by case basis. ;P On 22 May 2016 at 23:14, Love Nystrom wrote: > Server 2oo3 might

Re: [ros-dev] Actually a GOOD architecture.

Windows vs UNIX is like RISC vs CISC on cpus: each one has its flaws and advantages. The unix api philosophy is to keep the functions as simple as possible, and achieve the same tasks through serquences of configuration calls, rather than big monolithic APIs that have the settings all specified

Re: [ros-dev] 4th scenario

"Small companies and home servers" would often just be retail desktop machines using home/pro editions (XP) instead of server editions. On 23 May 2016 at 10:31, Riccardo Paolo Bestetti wrote: > Il 22/05/2016 23:14, Love Nystrom ha scritto: > > Server 2oo3 might not be

Re: [ros-dev] 4th scenario

Wouldn't that make people MORE interested in using reactos if it becomes a way for them to have NT6, without pirating or buying Windows? On 23 May 2016 at 14:21, Love Nystrom wrote: > Ok, I can understand if it has become uncommon in rich parts of the world > like Europe

Re: [ros-dev] Pale Moon drops ReactOS support

If we do NT6, we may want to have latest NT6 instead of trying to stick to an older one and having the same deprecation issue in a couple years? Also, what about the "idea" of keeping the majority of the kernel and large part of the usermode NT5, but having compatibility profiles that

Re: [ros-dev] Pale Moon drops ReactOS support

t; >>> Especially in new parts, as it would mean that something is written for >>> NT5 now, and first thing we do next is upgrade it to NT6. >>> >>> >>> >>> >>> >>> On Thu, May 12, 2016 at 6:39 PM, Zachary Gorden &

Re: [ros-dev] UEFI Bootmgr vs. FreeLdr

No it does not imply that, but chances are it will regardless. On 6 February 2017 at 05:05, Thomas Mueller wrote: > > Seeing the recent UEFI Bootmgr work in trunk, I was wondering about its > > design. > > Will that be a UEFI-only boot loader or eventually replace/merge

Re: [ros-dev] Bootlogos for FOSDEM (was: "RE: FOSDEM 2017 - It's happening!")

Is the use of the logo that way allowed by them? On 28 Jan 2017 5:04 p.m., "Hermès BÉLUSCA-MAÏTO" wrote: > Hello everyone, > > Upon an idea by Jared Smudde I modified a bit the ReactOS bootlogo to > incorporate in addition the FOSDEM logo in it. See >

Re: [ros-dev] Problems in Build Tutorial

Also, the output-blah-blah folder is only used if you run the configure command right on the sources folder. I prefer to have dedicated build output folders. My reactos development setup looks like: F:\reactos\ rosbe\ sources\ build\ mingw-x86-ninja vs14-x86-msbuild vs14-x86-ninja ... So in my

Re: [ros-dev] Microsoft switched to Git

in git". >> >> git commit -a -m "[BOOTLIB] Fix yet another bug]" >> git push >> >> Done. >> >> Best regards, >> Alex Ionescu >> >> >> On Wed, Feb 15, 2017 at 3:48 PM, David Quintana (gigaherz) >> <gigah...@gm

Re: [ros-dev] Microsoft switched to Git

LOL! Didn't the chromium people did just that earlier? On 25 February 2017 at 02:12, Alex Ionescu wrote: > I think I'm going to upload two PDF files to prove my point. > > On Thu, Feb 16, 2017 at 11:25 PM Hermès BÉLUSCA-MAÏTO < > hermes.belu...@sfr.fr> wrote: > >> Hi !

Re: [ros-dev] Microsoft switched to Git

odel it in that way, and so much more if you decide to model it >> in other ways. >> >> >> >> Ged. >> >> >> >> >> >> *From:* Ros-dev [mailto:ros-dev-boun...@reactos.org] *On Behalf Of *David >> Quintana (gigaherz) >>

Re: [ros-dev] Microsoft switched to Git

I meant to add, I don't know if their opinion has softened with regards to Git, since that discusion. On 15 February 2017 at 11:47, David Quintana (gigaherz) <gigah...@gmail.com> wrote: > There was a talk last year, about the possibility of switching. At least > one long-time membe

Re: [ros-dev] Microsoft switched to Git

e checked recently? We > are talking vehemently against it here, right, not 'minor annoyance'? > Not calling anyone out here, would just love to hear some input on what > they want from the repository system. No pooflinging, promise. > > 2017-02-15 11:35 GMT+01:00 David Quintana (gigah

Re: [ros-dev] Microsoft switched to Git

back into 'trunk'. > > > -Original Message- > From: Ros-dev [mailto:ros-dev-boun...@reactos.org] On Behalf Of Colin > Finck > Sent: 15 February 2017 10:53 > To: ros-dev@reactos.org > Subject: Re: [ros-dev] Microsoft switched to Git > > Am 15.02.2017 um 11:35

Re: [ros-dev] Microsoft switched to Git

My command set is a bit more extended: - git clone -- similar to svn checkout into a new folder - git checkout -- for changing the current branch - git pull -- effectively the same as "svn update", xcept it gets the entire change history, not just the latest commit data - git push

Re: [ros-dev] MASM using longer opcode sequences than GAS

No idea about the encoding length, but I wonder why we don't just use NASM everywhere, instead of having two separate assemblers. On 17 January 2017 at 10:23, Colin Finck wrote: > Hi all, > > In order to make our ISOs flashable to USB drives and bootable from them > (cf.

Re: [ros-dev] ReactOS is participating in Google Summer of Code 2017

It seems Haiku has been accepted also ( https://twitter.com/haikuOS/status/836317241129959424). This will be a nice year for alternative operating systems in GSoC :3 On 27 February 2017 at 20:17, Aleksey Bragin wrote: > Congrats!! > That is really wonderful news. It's not

Re: [ros-dev] Opening up #reactos-dev to the public

I approve the idea. On 24 March 2017 at 11:21, Colin Finck wrote: > Hi all! > > As you all know, our #reactos-dev IRC channel has been a moderated IRC > channel for decades, and only operators (devs) and voiced people can > talk. While we always tried to keep discussions

Re: [ros-dev] Opening up #reactos-dev to the public

AM, Mark Jansen <learn0more+...@gmail.com > > > >> wrote: > >> > >>> We can always try it out? > >>> If it doesnt work, restoring it is a simple as setting a flag on the > >>> channel. > >>> > >>> On 24 Marc

Re: [ros-dev] Google summer of code.

Hmm... I seem to have missed this message yesterday. Hello Atemafac, we have a wiki page with information for gsoc students: https://reactos.org/wiki/Google_Summer_of_Code_2017 If you have any doubts you can ask here or on IRC. On 29 March 2017 at 14:33, katahiromz .

Re: [ros-dev] Opening up #reactos-dev to the public

; > > 25.03.2017, 15:52, "Robert Naumann" <gonzo...@gmail.com>: > There should simply be more devs in #reactos. Some are, but many are not. > Everyone of us is able to give voice to newbies and direct dev related > conversations to the dev channel. When we open this ch

Re: [ros-dev] Opening up #reactos-dev to the public

I strongly disagree with everything you said in that email. I'll reply inline On 25 March 2017 at 21:17, Alexander Rechitskiy wrote: > My original claim was that discussion about opening #reactos-dev is useless > because: > 1. Devs intentionally not pay attention to

Re: [ros-dev] Opening up #reactos-dev to the public

ly > #reactos, it’s because it was generally too noisy, etc… . If we remove the > moderation irc bit in #reactos-dev, you may expect the same phenomenon to > occur in #reactos-dev too. > > > > *De :* Ros-dev [mailto:ros-dev-boun...@reactos.org] *De la part de* David > Quintana (g

Re: [ros-dev] Legal advice concerning contribution to ReactOS

Hello, First of all, I'm not qualified to give you a definitive answer, and anything I say is only my personal belief. I'm not a lawyer or anything close to one. I'm jsut writing to give you an approximation of an answer while you wait for the proper answer by someone who is qualified. I believe

Re: [ros-dev] JIRA/FishEye upgrade on March 8

Nice! Awesome job Colin. :) On 18 March 2017 at 17:34, Colin Finck wrote: > Am 16.03.2017 um 10:39 schrieb Colin Finck: > > I expect general source code information to come back in a couple of > > hours. Indexing all diff information takes a little longer and I expect > > it

Re: [ros-dev] New ideas added to GSoC Ideas list

That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order to support 16bit (windows 3.1) applications, a whole other system is needed. On 16 March 2017 at 23:37, Javier Agustìn Fernàndez Arroyo wrote: > "-Implementing WoW16 support. I suppose that'll draw

Re: [ros-dev] New ideas added to GSoC Ideas list

Gettext-style translations are really really bad, because they use the original text (usually in english) as a translation key, which means they simply can not handle situations where the same english text needs different translations depending on where the text is used. And yes, I have come

Re: [ros-dev] JIRA/FishEye upgrade on March 8

No worries. Getting the thing setup correctly is worth any wait. On 16 March 2017 at 10:39, Colin Finck wrote: > Hi again! > > Mark's commit yesterday has revealed a misconfiguration of the FishEye > indexing. Namely it only indexed source code files up to 100 KB and his >

Re: [ros-dev] New ideas added to GSoC Ideas list

t; NTDVM, so win3.1 apps can be run too :) > > On Thu, Mar 16, 2017 at 11:49 PM, David Quintana (gigaherz) < > gigah...@gmail.com> wrote: > >> That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order >> to support 16bit (windows 3.1) applications, a whole

Re: [ros-dev] New ideas added to GSoC Ideas list

That second Windows should have been ros. On 17 March 2017 at 01:25, David Quintana (gigaherz) <gigah...@gmail.com> wrote: > Running windows inside a vdm window isn't the same as running the apps > directly in windows, as if they were native apps. > > On 17 March 2017 at 01:

Re: [ros-dev] Retiring rapps

The new rapps is a conversion to C++, with many cleanups in the codebase, and the ground work for a future overhaul in a potential GSoC project. On 3 Apr 2017 8:18 am, "Can Tasan" wrote: > Hi! What does new RAPPS bring compared to old one, could you summarize > main points?

Re: [ros-dev] Enabling themes in 3rd stage

Remember, people, that we can only really bundle things that have compatible licenses. We can't just add random themes off the internet to the release isos. On 31 July 2017 at 20:37, Giannis Adamopoulos < giannis.adamopou...@reactos.org> wrote: > So you volunteer to create a theme? > > > Hermès

Re: [ros-dev] "Note: LibreOffice 5.4 will be the last codeline to support Windows XP or Vista"

Or we can continue working on NT6 compatibility... ;P On 29 June 2017 at 17:29, Javier Agustìn Fernàndez Arroyo wrote: > Maybe se could send some mail to those proyects, something like "hey, XP > is dead but we are alive! ;)" > > El 29/06/2017 16:56, "Thomas Faber"

Re: [ros-dev] About the bootcd and livecd, and the 1st-stage GUI setup

I feel like the boot menu is going to be far too busy for the end user. I'd go with something closer to blah blah: - Install Now - Try without installing - Show advanced options... where: - Install now -- boots into the graphical installer (no desktop unless you cancel or

Re: [ros-dev] About the bootcd and livecd, and the 1st-stage GUI setup

Oh the "Cancel and boot from hard disk" could be on the main menu I suppose! On 4 July 2017 at 22:45, David Quintana (gigaherz) <gigah...@gmail.com> wrote: > I feel like the boot menu is going to be far too busy for the end user. > I'd go with something closer to > >

Re: [ros-dev] [ros-diffs] [ion] 74546: BL Library now works 100% in paging, protected mode. A picture is worth a thousand commits: http://i.imgur.com/Zx2nQ6x.jpg [BOOTLIB]: Add support for protocol op

Pff, just disable secure boot, and avoid hardware where secure boot can not be disabled. On 15 May 2017 at 12:28, Javier Agustìn Fernàndez Arroyo wrote: > Please tell me ReactOS won't have to buy a key from MS so that we are > authorized to boot into machines :p > > El

Re: [ros-dev] Status Meeting - rescheduled

Works for me. On 24 May 2017 at 11:38, Aleksey Bragin wrote: > Hello, > > I propose to reschedule our monthly meeting to Thursday next week (1st of > June), as tomorrow is a holiday in some countries, and also I have tight > meetings schedule this week. > > Regards, >

Re: [ros-dev] Rethinking our Git merge workflow

I vote for recommending devs to use pull requests, and to make it a semi-strict policy that devs who push directly to master should ALWAYS make sure to pull and rebase before pushing. I myself intend on almost exclusively contribute through pull requests. This means: 1. I'll push to my own

Re: [ros-dev] Rethinking our Git merge workflow

uming we can set it > > up so that merge is allowed with no reviews (those would be recommended, > > but enforcing them seems too much). > > > > Though I'm also okay with giving up the linear history idea altogether, > > or hosting the repo elsewhere (e.g. we cou

Re: [ros-dev] Rethinking our Git merge workflow

ea altogether, > or hosting the repo elsewhere (e.g. we could host a Bitbucket instance). > > > On 2017-09-14 17:48, David Quintana (gigaherz) wrote: > >> I vote for recommending devs to use pull requests, and to make it a >> semi-strict policy that devs who push directly

  1   2   >