Hi Steven
We've (ReactOS) already gone beyond the header issue with the
decision to do a vendor branch of WINE. With regards to doing the
same for ZLib and FreeType: well spotted! We should definitely do the
same there.
As I understand it, with a vendor import of WINE it doesn't matter to
us (Rea
Ok thanks for clearing that up. Since our priority is SDK/DDK we'll
probably be the main submitters of such code then.
Regards
Jason
--- Danny Smith <[EMAIL PROTECTED]> wrote:
> From: "Jason Filby"
> > The only thing that worries me is Danny saying that they're
Hi Vizzini
This sounds good to me. As you said, it seems like headers are the
big blocker here.
Regards
Jason
--- Vizzini <[EMAIL PROTECTED]> wrote:
> Steven and I spoke about this the other day, and I am in agreement
> with
> you, Dimitrie. I don't want to fork. We can use CVS to manage the
>
Hi Dimitrie
User32 and gdi32 are likely to be a problem as the bulk of our
implementation is in kernel mode win32k.sys.
Regards
Jason
--- "Dimitrie O. Paun" <[EMAIL PROTECTED]> wrote:
> On October 14, 2003 03:11 pm, Jason Filby wrote:
>
> > I agree that forking sh
Hi all
I agree that forking should be avoided at all costs. Of course it
will be unavoidable for lower level DLLs such as user32. I'm getting
the tail end of this discussion so someone please fill me in if I'm
missing some big issues. The big deal with be source control
differences between the two
