- Ros-dev - ReactOS.org

Re: [ros-dev] Microsoft switched to Git
by Alex Ionescu 15 Feb '17

15 Feb '17

On Wed, Feb 15, 2017 at 9:01 AM, Zachary Gorden <drakekaizer666(a)gmail.com> wrote: > Why is there a need for anything beyond "git commit" or "git push" or "git > pull" to do anything? Good question. I've never used any other git command other than those (except git checkout). Oh, that's lie, I've also used "git branch", just like on svn, to create a branch. Sounds like you've never actually used git? I've never rebased in my life, and I don't know what other commands even exist. Best regards, Alex Ionescu

2 1

Microsoft switched to Git
by Colin Finck 15 Feb '17

15 Feb '17

https://blogs.msdn.microsoft.com/bharry/2017/02/03/scaling-git-and-some-bac… I didn't expect Microsoft to switch to Git sooner than us..

6 16

Re: [ros-dev] Microsoft switched to Git
by Brandin L Claar 15 Feb '17

15 Feb '17

Just move everything to GitHub: https://github.com/blog/966-improved-subversion-client-support -brandin > On Feb 15, 2017, at 06:32, ros-dev-request(a)reactos.org wrote: > > Send Ros-dev mailing list submissions to > ros-dev(a)reactos.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.reactos.org/mailman/listinfo/ros-dev > or, via email, send a message with subject or body 'help' to > ros-dev-request(a)reactos.org > > You can reach the person managing the list at > ros-dev-owner(a)reactos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Ros-dev digest..." > > > Today's Topics: > > 1. Re: Microsoft switched to Git (Ged Murphy) > 2. Re: Microsoft switched to Git (David Quintana (gigaherz)) > 3. Re: Microsoft switched to Git (Colin Finck) > 4. Re: Microsoft switched to Git (David Quintana (gigaherz)) > 5. Re: Microsoft switched to Git (Colin Finck) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 15 Feb 2017 11:04:52 -0000 > From: "Ged Murphy" <gedmurphy.maillists(a)gmail.com> > To: "'ReactOS Development List'" <ros-dev(a)reactos.org> > Subject: Re: [ros-dev] Microsoft switched to Git > Message-ID: <004701d2877b$55983010$00c89030$(a)gmail.com> > Content-Type: text/plain; charset="utf-8" > > I think the easiest path is to switch to a centralized style model using git. > That is, we have a master copy (aka trunk) that gives the feel of our existing model. That would allow devs that prefer SVN to mostly continue working as before, and give the devs who want to use git in a more traditional way the ability to branch off and work in a git style manner, then sync their changes back into 'trunk'. > > > -----Original Message----- > From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of Colin Finck > Sent: 15 February 2017 10:53 > To: ros-dev(a)reactos.org > Subject: Re: [ros-dev] Microsoft switched to Git > >> Am 15.02.2017 um 11:35 schrieb David Quintana (gigaherz): >> The number doesn't matter. The ReactOS project can't afford to lost >> any long-time members. Git would be a benefit for all of us, but it >> has to be a benefit for ALL of us. > > Let's not forget: > > - Part of the reasons developers had against Git may have been resolved by now. > - Part of the problem may be that "Git is so different" to some devs, but I think this can be resolved by a detailed Wiki article showing how to do the same thing in SVN and Git. We already wrote such articles for TortoiseSVN after all! > - And finally, we first need a plan for a Git move that doesn't suck. We tried SubGit and it failed for us. Then there is the "Merge workflow", which is supported very well by all tools, but creates a lot of parallel history. The "Rebase workflow" is more like what SVN does (keeping a linear history), but no idea how to enforce that with TortoiseGit. > > I think if a team could look after these things and help moving each and every developer towards Git, it may even be doable for us. > > Cheers, > > Colin > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------ > > Message: 2 > Date: Wed, 15 Feb 2017 12:18:40 +0100 > From: "David Quintana (gigaherz)" <gigaherz(a)gmail.com> > To: ReactOS Development List <ros-dev(a)reactos.org> > Subject: Re: [ros-dev] Microsoft switched to Git > Message-ID: > <CADD3+ruo18pQos1QO+jCHg5V2-hyrrjSZ7Va1pfgm+tprDbDZw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > My belief is that the best path would be: > > Phase 0: This is how we are now. We have SVN master (trunk), and a > read-only git mirror, and a semi-updated github mirror for when a > contributor really wants to submit git PRs. > > Phase 1: Switch to using Git with PRs for submitting patches (Github's PR > system is really really nice these days, but other solutions exist). Setup > a SVN mirror "bot" that creates one svn commit for each push/merge detected > in the master branch, and allows the buildbots to continue working as they > do now. > > This would allow the existing svn-patch workflow to continue working, but > commits on svn wouldn't be allowed anymore. Developers are expected to at > least TRY to learn to use git (it's not that hard! I promise!). > > Phase 2: We switch the buildbots and testbots to pull from git, enable > testbot access for git PRs (such as with a github bot that responds to > "@rosbot runtest" or similar). The SVN mirror remains, for archival > purposes, but git commits aren't merged so regularly. Release tags/branches > can still be published through SVN, for ease of access. > > Phase 3: Everyone ends up agreeing that maintaining the svn mirror is no > longer worth the effort. > > Of course, anything like this will only happen if the entire team agrees to > it. > > On 15 February 2017 at 12:04, Ged Murphy <gedmurphy.maillists(a)gmail.com> > wrote: > >> I think the easiest path is to switch to a centralized style model using >> git. >> That is, we have a master copy (aka trunk) that gives the feel of our >> existing model. That would allow devs that prefer SVN to mostly continue >> working as before, and give the devs who want to use git in a more >> traditional way the ability to branch off and work in a git style manner, >> then sync their changes back into 'trunk'. >> >> >> -----Original Message----- >> From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of Colin >> Finck >> Sent: 15 February 2017 10:53 >> To: ros-dev(a)reactos.org >> Subject: Re: [ros-dev] Microsoft switched to Git >> >>> Am 15.02.2017 um 11:35 schrieb David Quintana (gigaherz): >>> The number doesn't matter. The ReactOS project can't afford to lost >>> any long-time members. Git would be a benefit for all of us, but it >>> has to be a benefit for ALL of us. >> >> Let's not forget: >> >> - Part of the reasons developers had against Git may have been resolved by >> now. >> - Part of the problem may be that "Git is so different" to some devs, but >> I think this can be resolved by a detailed Wiki article showing how to do >> the same thing in SVN and Git. We already wrote such articles for >> TortoiseSVN after all! >> - And finally, we first need a plan for a Git move that doesn't suck. We >> tried SubGit and it failed for us. Then there is the "Merge workflow", >> which is supported very well by all tools, but creates a lot of parallel >> history. The "Rebase workflow" is more like what SVN does (keeping a linear >> history), but no idea how to enforce that with TortoiseGit. >> >> I think if a team could look after these things and help moving each and >> every developer towards Git, it may even be doable for us. >> >> Cheers, >> >> Colin >> >> _______________________________________________ >> Ros-dev mailing list >> Ros-dev(a)reactos.org >> http://www.reactos.org/mailman/listinfo/ros-dev >> >> >> _______________________________________________ >> Ros-dev mailing list >> Ros-dev(a)reactos.org >> http://www.reactos.org/mailman/listinfo/ros-dev >> >

6 7

Re: [ros-dev] Microsoft switched to Git
by Alex Ionescu 15 Feb '17

15 Feb '17

How about I leave if we DON'T switch to Git? I fucking hate SVN now (read my e-mail from 8 years ago on this topic, lol!). Best regards, Alex Ionescu On Wed, Feb 15, 2017 at 3:32 AM, Colin Finck <colin(a)reactos.org> wrote: > Am 15.02.2017 um 12:18 schrieb David Quintana (gigaherz): >> Setup a SVN mirror "bot" that creates one svn commit for each push/merge >> detected in the master branch, and allows the buildbots to continue >> working as they do now. > > Let's not have a Git repository with a parallel SVN mirror again. SubGit > tried to accomplish this as a professional solution and it failed for us. > > There is no reason to take extra care of the Buildslaves at all. > The same infra people, who would do the switch to Git, could also change > the Buildslaves to use Git instead of SVN in the course of that. > > > - Colin > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev

1 0

(no subject)
by katahiromz . 15 Feb '17

15 Feb '17

Microsoft will use GVFS (Git Virtual File System) to manage their huge Git repository.

1 0

FishEye DB being rebuilt
by Colin Finck 14 Feb '17

14 Feb '17

Hi all! As this is taking longer than expected, I should give a notice: In an attempt to restart hanging FishEye yet another time yesterday, its stored database of the reactos SVN repository was corrupted... I'm rebuilding it since yesterday evening, but parsing all the diffs is a long process. Can't give any ETA yet. So far, only commit information without diff is available at code.reactos.org. Cheers, Colin

4 7

Re: [ros-dev] [ros-diffs] [ekohl] 73795: [NTOSKRNL] Implement IopGetDeviceRelations().
by Thomas Faber 14 Feb '17

14 Feb '17

On 2017-02-13 23:38, ekohl(a)svn.reactos.org wrote: > + _SEH2_TRY > + { > + Relations = RelationsData->Relations; > + BufferSize = RelationsData->BufferSize; > + Buffer = RelationsData->Buffer; > + > + ProbeForWrite(RelationsData->Buffer, > + RelationsData->BufferSize, > + sizeof(CHAR)); > + } You need to use the local 'Buffer' and 'BufferSize' variables in the probe or you get a race condition. > + Status = IopInitiatePnpIrp(DeviceObject, > + &IoStatusBlock, > + IRP_MN_QUERY_DEVICE_RELATIONS, > + &Stack); > + if (!NT_SUCCESS(Status) || Status == STATUS_PENDING) > + { > + DPRINT1("IopInitiatePnpIrp() failed (Status 0x%08lx)\n", Status); > + goto done; > + } Failing on STATUS_PENDING seems broken. IoStatusBlock will go out of scope and the DeviceRelations set by the driver will be leaked. > + if (RequiredSize > 0) > + RequiredSize += sizeof(WCHAR); Not sure I understand the >0 condition. Best, Thomas

1 0

UEFI Bootmgr vs. FreeLdr
by Colin Finck 06 Feb '17

06 Feb '17

Hi all! 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 with FreeLdr to provide a common boot loader for BIOS and UEFI systems? Will it simply follow all design principles of the NT6+ boot loader or also implement some own ideas or take over those from FreeLdr? For instance, I totally like FreeLdr's configuration through INI files and would prefer that any day over NT6+ BCD registry hives. Cheers, Colin

3 2

Google Summer of Code 2017
by Colin Finck 03 Feb '17

03 Feb '17

Hi all! Google Summer of Code 2017 is fast approaching, with February 9 being the deadline for projects to apply. With our record of successfully completing all 4 ideas (msahci, NTFS, lwIP, USB) last year, we should definitely apply again. Aleksey and Amine have already begun filling out the application form. Based on the 2016 ideas Wiki page, we have also created a new ideas page at https://reactos.org/wiki/Google_Summer_of_Code_2017_Ideas Please share your thoughts on these and add anything that's missing. What we now need are possible mentors. Who would be available for this? Cheers, Colin

4 4

About JIRA Account
by JasonQSY 01 Feb '17

01 Feb '17

Hi, I’m interested in ros dev now and it seems that fixing small bugs could be a good start. Could I have a JIRA account and have a look at the issues? Or any suggestions about jobs could be done by a newcomer? - JasonQSY

2 1

Re: [ros-dev] [ros-diffs] [tfaber] 73631: [0.4.4] - Mask WndProc exceptions CORE-11915
by Alex Ionescu 31 Jan '17

31 Jan '17

In Windows, this is actually part of the AppCompat database. there's a flag in tagWND that enables/disables this behavior. Best regards, Alex Ionescu On Mon, Jan 30, 2017 at 3:35 AM, <tfaber(a)svn.reactos.org> wrote: > Author: tfaber > Date: Mon Jan 30 11:35:05 2017 > New Revision: 73631 > > URL: http://svn.reactos.org/svn/reactos?rev=73631&view=rev > Log: > [0.4.4] > - Mask WndProc exceptions > CORE-11915 > > Modified: > branches/ros-branch-0_4_4/reactos/win32ss/user/user32/windows/message.c > > Modified: branches/ros-branch-0_4_4/reactos/win32ss/user/user32/windows/message.c > URL: http://svn.reactos.org/svn/reactos/branches/ros-branch-0_4_4/reactos/win32s… > ============================================================================== > --- branches/ros-branch-0_4_4/reactos/win32ss/user/user32/windows/message.c [iso-8859-1] (original) > +++ branches/ros-branch-0_4_4/reactos/win32ss/user/user32/windows/message.c [iso-8859-1] Mon Jan 30 11:35:05 2017 > @@ -1464,20 +1464,15 @@ > > if (PreResult) goto Exit; > > - if (!Dialog) > - Result = CALL_EXTERN_WNDPROC(WndProc, AnsiMsg.hwnd, AnsiMsg.message, AnsiMsg.wParam, AnsiMsg.lParam); > - else > - { > _SEH2_TRY > { > Result = CALL_EXTERN_WNDPROC(WndProc, AnsiMsg.hwnd, AnsiMsg.message, AnsiMsg.wParam, AnsiMsg.lParam); > } > _SEH2_EXCEPT(EXCEPTION_EXECUTE_HANDLER) > { > - ERR("Exception Dialog Ansi %p Msg %d pti %p Wndpti %p\n",WndProc,Msg,GetW32ThreadInfo(),pWnd->head.pti); > + ERR("Exception when calling Ansi WndProc %p Msg %d pti %p Wndpti %p\n",WndProc,Msg,GetW32ThreadInfo(),pWnd->head.pti); > } > _SEH2_END; > - } > > if (Hook && MsgOverride) > { > @@ -1518,20 +1513,15 @@ > > if (PreResult) goto Exit; > > - if (!Dialog) > - Result = CALL_EXTERN_WNDPROC(WndProc, hWnd, Msg, wParam, lParam); > - else > - { > _SEH2_TRY > { > Result = CALL_EXTERN_WNDPROC(WndProc, hWnd, Msg, wParam, lParam); > } > _SEH2_EXCEPT(EXCEPTION_EXECUTE_HANDLER) > { > - ERR("Exception Dialog unicode %p Msg %d pti %p Wndpti %p\n",WndProc, Msg,GetW32ThreadInfo(),pWnd->head.pti); > + ERR("Exception when calling unicode WndProc %p Msg %d pti %p Wndpti %p\n",WndProc, Msg,GetW32ThreadInfo(),pWnd->head.pti); > } > _SEH2_END; > - } > > if (Hook && MsgOverride) > { > @@ -1611,20 +1601,15 @@ > > if (PreResult) goto Exit; > > - if (!Dialog) > - Result = CALL_EXTERN_WNDPROC(WndProc, hWnd, Msg, wParam, lParam); > - else > - { > _SEH2_TRY > { > Result = CALL_EXTERN_WNDPROC(WndProc, hWnd, Msg, wParam, lParam); > } > _SEH2_EXCEPT(EXCEPTION_EXECUTE_HANDLER) > { > - ERR("Exception Dialog Ansi %p Msg %d pti %p Wndpti %p\n",WndProc,Msg,GetW32ThreadInfo(),pWnd->head.pti); > + ERR("Exception when calling Ansi WndProc %p Msg %d pti %p Wndpti %p\n",WndProc,Msg,GetW32ThreadInfo(),pWnd->head.pti); > } > _SEH2_END; > - } > > if (Hook && MsgOverride) > { > @@ -1672,20 +1657,15 @@ > > if (PreResult) goto Exit; > > - if (!Dialog) > - Result = CALL_EXTERN_WNDPROC(WndProc, UnicodeMsg.hwnd, UnicodeMsg.message, UnicodeMsg.wParam, UnicodeMsg.lParam); > - else > - { > _SEH2_TRY > { > Result = CALL_EXTERN_WNDPROC(WndProc, UnicodeMsg.hwnd, UnicodeMsg.message, UnicodeMsg.wParam, UnicodeMsg.lParam); > } > _SEH2_EXCEPT(EXCEPTION_EXECUTE_HANDLER) > { > - ERR("Exception Dialog unicode %p Msg %d pti %p Wndpti %p\n",WndProc, Msg,GetW32ThreadInfo(),pWnd->head.pti); > + ERR("Exception when calling unicode WndProc %p Msg %d pti %p Wndpti %p\n",WndProc, Msg,GetW32ThreadInfo(),pWnd->head.pti); > } > _SEH2_END; > - } > > if (Hook && MsgOverride) > { > >

1 0

Re: [ros-dev] Bootlogos for FOSDEM (was: "RE: FOSDEM 2017 - It's happening!")
by Hermès BÉLUSCA-MAÏTO 31 Jan '17

31 Jan '17

Hi ! After this successful poll, the winner bootlogo is without doubt the (d) version :-) I have committed it here : https://svn.reactos.org/svn/reactos?view=revision <https://svn.reactos.org/svn/reactos?view=revision&revision=73639> &revision=73639 This is the file “1.bmp”. As the bootlogo and the other boot images are 16-colour (palette) bitmaps, I had to adjust the palette of the other ones too (because they are occasionally rendered together). Cheers, Hermès De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Daniel Franzini Envoyé : lundi 30 janvier 2017 17:20 À : ReactOS Development List Objet : Re: [ros-dev] Bootlogos for FOSDEM (was: "RE: FOSDEM 2017 - It's happening!") I'd go with (h) first then (d) second. I agree with David but I prefer the (h) version of the logo. P.S.: I don't think that my opinion matters that much. On Mon, Jan 30, 2017 at 2:08 PM, David Quintana (gigaherz) <gigaherz(a)gmail.com> wrote: Ah I just realised I never wrote which version I prefer: d. Reason: it's more symmetric -- fills in the empty space to the right, corresponding to the copyright notice on the left. On 30 January 2017 at 16:40, Yaroslav Veremenko <yaroslav(a)veremenko.info> wrote: I like c/d (preferably more d). Yaroslav -----Original Message----- From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of Hermes BELUSCA-MAITO Sent: Saturday, January 28, 2017 8:29 AM To: 'ReactOS Development List' <ros-dev(a)reactos.org> Subject: [ros-dev] Bootlogos for FOSDEM (was: "RE: FOSDEM 2017 - It's happening!") 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 http://polariton.ad-l.ink/6WhjqNRrM/image.png or the attached file. I have done several versions and I would like to hear what you think from them (if possible, make a choice). Regards, Hermès -----Message d'origine----- De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Colin Finck Envoyé : jeudi 26 janvier 2017 00:16 À : 'ReactOS Development List' Objet : [ros-dev] FOSDEM 2017 - It's happening! Hi all! Hermès and me have just decided to go to FOSDEM this year. Which is a really good idea considering that we have a booth to staff there ;) Planning is currently happening at https://docs.google.com/document/d/1ofYUc7j0XwDH9SmNlGzNZlO8jOGhoPUn7KTRcFm… Just request access if you're a ReactOS member and like to add or comment stuff there. Hermès will be preparing an ISO in the upcoming days. Please test current trunk to see if any last minute fixes need to go there. If you have ideas what cool apps we shall show at FOSDEM, please also share them here. We will go with burning and giving away CDs again (hopefully the last time before USBs do it). I hope that this definite plan will also motivate others to join us or visit our booth! :) Cheers, Colin _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev -- Daniel "Let us change our traditional attitude to the construction of programs. Instead of imagining that our main task is to instruct a computer what to do, let us concentrate rather on explaining to human beings what we want a computer to do." (Donald Knuth) "Yes, technogeeks can be funny, even if only to each other." (http://www.boogieonline.com/revolution/science/humor/)" "Man is driven to create; I know I really love to create things. And while I'm not good at painting, drawing, or music, I can write software." (Yukihiro Matsumoto, a.k.a. ``Matz'')

1 0

Re: [ros-dev] FOSDEM 2017 - It's happening!
by hermes.belusca＠sfr.fr 30 Jan '17

30 Jan '17

We use FreeLDR for the RAM booting, which loads in RAM an ISO (not a HDD image yet). For the LiveCD for example, the following lines can be added into freeldr.ini: [Operating Systems] ... LiveCD_RamDisk="LiveCD in RAM" ... [LiveCD_RamDisk] BootType=Windows2003 SystemPath=ramdisk(0)\reactos Options=/MININT /RDPATH=livecd\livecd.iso /RDEXPORTASCD FreeLdr will load the "livecd\livecd.iso" file from the boot drive (a USB key for example...) (the switch '/RDEXPORTASCD' explicitely specifies that the file is loaded as an ISO image, with read-only access, etc...). Then, "ramdisk(0)\reactos" specifies that the kernel etc... will be loaded from the "reactos" directory inside the root directory constituted by the ramdisk, once the ramdisk is loaded. Regards, Hermès

2 1

Re: [ros-dev] Google Summer of Code 2017
by Alex Ionescu 30 Jan '17

30 Jan '17

So we said we 'completed msahci' but the code is languishing in a branch... Best regards, Alex Ionescu On Thu, Jan 26, 2017 at 3:13 PM, Colin Finck <colin(a)reactos.org> wrote: > Am 26.01.2017 um 23:46 schrieb Yaroslav Veremenko: >> Just a side note, looking at the list. I think you should remove SSH Service from it as Microsoft is currently poring OpenSSH on NT > > Yep, done that. Thanks for the hint! > > > - Colin > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev

2 1

Bootlogos for FOSDEM (was: "RE: FOSDEM 2017 - It's happening!")
by Hermès BÉLUSCA-MAÏTO 30 Jan '17

30 Jan '17

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 http://polariton.ad-l.ink/6WhjqNRrM/image.png or the attached file. I have done several versions and I would like to hear what you think from them (if possible, make a choice). Regards, Hermès -----Message d'origine----- De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Colin Finck Envoyé : jeudi 26 janvier 2017 00:16 À : 'ReactOS Development List' Objet : [ros-dev] FOSDEM 2017 - It's happening! Hi all! Hermès and me have just decided to go to FOSDEM this year. Which is a really good idea considering that we have a booth to staff there ;) Planning is currently happening at https://docs.google.com/document/d/1ofYUc7j0XwDH9SmNlGzNZlO8jOGhoPUn7KTRcFm… Just request access if you're a ReactOS member and like to add or comment stuff there. Hermès will be preparing an ISO in the upcoming days. Please test current trunk to see if any last minute fixes need to go there. If you have ideas what cool apps we shall show at FOSDEM, please also share them here. We will go with burning and giving away CDs again (hopefully the last time before USBs do it). I hope that this definite plan will also motivate others to join us or visit our booth! :) Cheers, Colin _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

9 10

FOSDEM Announcement on website
by Colin Finck 30 Jan '17

30 Jan '17

Hi all, Someone please announce our FOSDEM presence next Saturday and Sunday (February 4/5) on the website. Hermès and me will be there representing the ReactOS Project at our shared ReactOS/HaikuOS booth in the K Building, together with Adrien Destugues and François Revol from HaikuOS. - Colin

1 0

Re: [ros-dev] [ros-diffs] [tfaber] 73607: [NTOS:MM] - Support MmSpecialPoolTag == '*' to mean all tags. By Serge Gautherie. CORE-12711 #resolve
by Alex Ionescu 30 Jan '17

30 Jan '17

On Sat, Jan 28, 2017 at 5:08 AM, <tfaber(a)svn.reactos.org> wrote: > MmSpecialPoolTag We should add support for '?'. This is just a few extra lines of code. Best regards, Alex Ionescu

1 0

font penalty system
by katahiromz . 28 Jan '17

28 Jan '17

Hello, this is katahiromz aka a Win32 programmer and tester from Japan. At first, check out the x12 patch of CORE-6621. Please take a look at the WeightFromStyle and GetFontPenalty functions. The "DejaVu Sans Mono" fonts are in use, as substitute fonts. There is a problem. The penalty weight of "DejaVu Sans Mono Oblique" is lighter than one of "DejaVu Sans Mono Book" in the current penalty system of Table 1. The "Oblique" penalty is 4 of Italic Penalty. The "Book" penalty is 3 * ((400 - 350) / 10) == 15 of Weight Penalty. So, Oblique < Book! Should we adjust Italic Penalty to 16 or more?

1 0

Problems in Build Tutorial
by JasonQSY 27 Jan '17

27 Jan '17

Hi, I’m a newcomer to ros-dev and currently try to build reactos. It is ok for me but I think there might be slight problems in the tutorial. > cd output-MinGW-i386 I think it maybe cd output-MinGW-i386/reactos . Running `ninja` under `output-MinGW-i386` fails. > generates a bootable ReactOS ISO file (bootcd.iso) placed into the output directory I find `bootcd.iso` under `reactos` instead of `reactos/output`. Are they outdated? - JasonQSY

4 3

Office 2010 support
by Colin Finck 27 Jan '17

27 Jan '17

Hi all! During the monthly meeting yesterday, there was a high demand for full Office 2010 support under ReactOS. Let's call that Word, Excel and PowerPoint for now. If we get these applications to work, the potential customer may generously sponsor the ReactOS Project. While Hermès is already working on getting Word 2010 support as part of the ReactOS Community Edition, he has shown that this task easily splits into many subtasks, like full NTLM implementation, Printing, etc. If anybody volunteers to work on these, or otherwise contribute to get the full Office 2010 to work under ReactOS, we would be willing to support this with our foundation funds too! As a first step, let's make a list of related tasks and add them to https://jira.reactos.org/browse/CORE-12279 Hermès can probably help here. If you have other ideas on how to help with Office 2010, don't hesitate to tell. This needs teamwork! Let's not miss this opportunity to make ReactOS usable for the mass! - Colin

1 0

FOSDEM 2017 - It's happening!
by Colin Finck 27 Jan '17

27 Jan '17

Hi all! Hermès and me have just decided to go to FOSDEM this year. Which is a really good idea considering that we have a booth to staff there ;) Planning is currently happening at https://docs.google.com/document/d/1ofYUc7j0XwDH9SmNlGzNZlO8jOGhoPUn7KTRcFm… Just request access if you're a ReactOS member and like to add or comment stuff there. Hermès will be preparing an ISO in the upcoming days. Please test current trunk to see if any last minute fixes need to go there. If you have ideas what cool apps we shall show at FOSDEM, please also share them here. We will go with burning and giving away CDs again (hopefully the last time before USBs do it). I hope that this definite plan will also motivate others to join us or visit our booth! :) Cheers, Colin

4 4

Status Meeting (January 2017)
by Aleksey Bragin 23 Jan '17

23 Jan '17

Hello, Let me invite you to the monthly status meeting taking place today, 26th of January, 19:00 UTC. We skipped the last meeting because of holidays and unavailability of people. IRC service will only be started shortly before the meeting. Your participation passwords and server address will be emailed to you shortly before the meeting starts, and they are going to be different once again as they are not stored in any database. Hopefully it's not much of inconvenience. Alternatively we'll do it in #reactos-meeting on Freenode, depending on our admins mood. Please send agenda proposals to me before the meeting so we don't waste time trying to setup the agenda directly during the meeting. Regards, Aleksey Bragin

1 1

MASM using longer opcode sequences than GAS
by Colin Finck 18 Jan '17

18 Jan '17

Hi all, In order to make our ISOs flashable to USB drives and bootable from them (cf. CORE-12648), I'm currently overhauling our ISO boot sector "isoboot.S". This adds a lot of code and while I stay in the 2K size limit when assembling it with GAS, I break it with MASM. Disassembling the assembled files shows the difference. A line like: mov word ptr ds:[GetlinsecPtr], ax is assembled by GAS to: A35B50 mov [0x505b],ax while MASM does this: 67A35B500000 mov [dword 0x505b],ax Is there any option to enforce the shorter opcode sequence for MASM too? The code uses a lot of similar MOVs and this seems to be the only reason why I break the 2K size limit with MASM. If there is no such option, what are the advantages of using MASM for our MSVC build anyway? Can't we just use GAS for both or decide on a common third-party assembler (NASM) for our assembly files? Cheers, Colin

4 4

Re: [ros-dev] [ros-diffs] [jimtabor] 73532: [NtUser] - Fix menu surfing while using MS Office 2003. See CORE-12085 and CORE-12071.
by Thomas Faber 13 Jan '17

13 Jan '17

On 2017-01-13 05:06, jimtabor(a)svn.reactos.org wrote: > VOID FASTCALL > IntSendChildNCPaint(PWND pWnd) > { > + PWND Child; > + HWND *List, *phWnd; > + > + List = IntWinListChildren(UserGetDesktopWindow()); > + if ( List ) > + { > + for (phWnd = List; *phWnd; ++phWnd) > + { > + Child = ValidateHwndNoErr(*phWnd); > + if ( Child && Child->hrgnUpdate == NULL && Child->state & WNDS_SENDNCPAINT) > + { > + USER_REFERENCE_ENTRY Ref; > + UserRefObjectCo(Child, &Ref); > + IntSendNCPaint(Child, HRGN_WINDOW); > + UserDerefObjectCo(Child); > + } > + } > + } You leak List here, both in the normal case and in the exception-during-callout case.

2 1

Was the idea to sertup USB-flash drive giveaway with ReactOS on FOSDEM buried?
by Alexander Rechitskiy 11 Jan '17

11 Jan '17

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev