Summary of MSRPC / DCE/RPC interoperability / Applicability of FreeDCE for Wine (DCOM)

Luke Kenneth Casson Leighton lkcl at
Tue Jan 25 03:04:02 CST 2005

On Tue, Jan 25, 2005 at 01:29:03PM +0900, Mike McCormack wrote:
> Luke Kenneth Casson Leighton wrote:
> >hi, in case you looked at the number of emails exchanged on FreeDCE
> >and freaked out, here's a summary.  if you feel that there are any
> >relevant points missing or incorrect, please _do_ speak up.
> There's only one thing that counts for Wine, and that is patches that 
> improve Wine.  A grand scheme is nice, but it means nothing without patches.
> And each patch should improve something and make Wine work better in its 
> own right.  Set low goals for each patch. Having something working now 
> is more valuable than having a chance at having something work in the 
> future.
> Look forward to seeing your nice incremental improvements, submitted as 
> bite sized patches to wine-patches.

mike, hi,

what is my incentive to do that?

i am presenting the wine team with an opportunity to save time and effort,
because i feel a sense of responsibility and a duty to do so: i hate to
see people waste time and effort duplicating code - _especially_ people who
do so in a free software environment.

as things stand, however, the amount of effort i can spend it
ends there, however, because the last time i was paid and actively
encouraged to work on free software ended in 2000.

i would therefore be delighted to be presented with an
opportunity and an incentive to provide you with as many nice
incremental improvements and bite sized patches to wine-patches
as you see fit to receive, evaluate and accept - especially
an opportunity that saves other people stacks of time, effort
and money.


More information about the wine-devel mailing list