Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

2010-07-25 Thread Aleksey Bragin
Let cmake branch be actual cmake experiment, not an awesome attempt to fix whole ReactOS at once WBR, Aleksey Bragin. From: Zachary Gorden Sent: Sunday, July 25, 2010 9:45 PM To: ReactOS Development List Subject: Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup

Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

2010-07-25 Thread Ged Murphy
Sent:* Sunday, July 25, 2010 9:45 PM > *To:* ReactOS Development List > *Subject:* Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch > forcmake bringup. > > I also support a reshuffling of the directories, but not in the cmake > branch. Let that be used JUST for getting cmak

Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

2010-07-25 Thread Zachary Gorden
Do you have any specific proposals, Ged? ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

2010-07-30 Thread Adam Kachwalla
unday, July 25, 2010 9:45 PM To: ReactOS Development List Subject: Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup. I also support a reshuffling of the directories, but not in the cmake branch.  Let that be used JUST for getting cmake up and running and if/once that is

Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

2010-07-30 Thread Gabriel ilardi
. To: ros-dev@reactos.org; gedmur...@gmail.com Date: Fri, 30 Jul 2010 21:05:10 +1000 From: geekdun...@gmail.com Subject: Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup. I might be a bit of a n00b but at this stage, I also support this restructuring of the tree. I

Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

2010-07-30 Thread Jérôme Gardou
Having a proper build system and a good tree structure is a mandatory step to work efficiently. As long as we have neither of them, it is a priority. That's just my opinion, though... Gabriel ilardi wrote: I think that the tree reshuffle should be done separately from the cmake branch. I also

Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

2010-07-30 Thread victor martinez
Answers inlined. > Having a proper build system and a good tree structure is a mandatory > step to work efficiently. As long as we have neither of them, it is a > priority. > That's just my opinion, though... In my opinion there are more mandatory things: 1) Avoiding to commit partial

Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

2010-07-30 Thread Andrew Faulds
On 30 July 2010 22:44, victor martinez wrote: > > > On the other hand ReactOS is in a really bad shape form a user point > > > of view and all the resources should focus on fix the most important > > > bugs and regressions listed in http://www.reactos.org/wiki/Buglist. > > > The rest of the things

Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

2010-07-30 Thread Ged Murphy
On 30 July 2010 22:44, victor martinez wrote: > > > > In my opinion there are more mandatory things: > > > > > 1) Avoiding to commit partial code. For partial code or > partial-semi-working features you can use branchs. > 2) Just tested code commited to trunk. You can make (ab)use of testers or >

Re: [ros-dev] [ros-diffs] [akhaldi] 48236: Create a branch forcmake bringup.

2010-07-31 Thread Bernd Blaauw
Op 30-7-2010 23:52, Andrew Faulds schreef: We need this, else it may be another millennia until 0.3.12... -- Nothing wrong with celebrating (likely soon upcoming) commit 50.000 by releasing it as 0.3.12 or so ^^. ___ Ros-dev mailing list Ros-dev