On Monday, 14 October 2013 9:50 PM, Ricardo Filipe wrote:
>I'd be more than happy to help you review your patches, although I am no
>wineconsole expert, I believe I could help you get your changes into wine.
>Contact me if no better offer comes around :) cheers
Hello Ricardo,
Thank you for you
ize that wineconsole is only a minor
> focus of development.
>
> Hugh
>
> -
>
> Hi everyone,
>
> I just wanted to know if anyone would mind helping/mentoring me with a few
> small patches.
>
> I am working primarily on wi
Can anyone help me on this? I do realize that wineconsole is only a minor focus
of development.
Hugh
-
Hi everyone,
I just wanted to know if anyone would mind helping/mentoring me with a few
small patches.
I am working primarily on
Hi everyone,
I just wanted to know if anyone would mind helping/mentoring me with a few
small patches.
I am working primarily on wineconsole's screen buffer problems (to which I
believe I have the solution), but am also looking at implementing some stub
Win32 console functions found in
Hi Dan,
Op 28-02-11 21:41, Dan Kegel schreef:
So, shall I do the honors?
I've already been applying wine for summer of code this year, haven't
finished it up though, you could always join as second backup admin.
However I'd like everyone to have another look at our
http://wiki.winehq.org/Sum
So, shall I do the honors?
-- Forwarded message --
From: Carol Smith
Date: Mon, Feb 28, 2011 at 12:35 PM
Subject: Applications for Mentoring Organizations Now Being Accepted
To: Google Summer of Code Announce
Hi all,
We're pleased to announce the applications for ment
This looks interesting...
-- Forwarded message --
From: Carol Smith
Date: Mon, Oct 18, 2010 at 3:10 PM
Subject: Invitation: Apply to be a Mentoring Organization for GCI
To: Google Summer of Code Mentors List
Hi everyone,
Starting today we are accepting applications from
I hadn't see any talk about this, so passing this along from Google:
--
-Austin
-- Forwarded message --
From: Carol Smith
Date: Mon, Oct 18, 2010 at 8:10 AM
Subject: Invitation: Apply to be a Mentoring Organization for GCI
To: Google Summer of Code Mentors List
Hi eve
Am Dienstag 15 Mai 2007 02:33 schrieb Ivan Gyurdiev:
> > What Stefan says about discussing patches
> > is true--it helps if there's not a lot of debate around a patch.
>
> This quote should go down in the history of open source :)
> I hope the word you're looking for is "controversy".
Yes, "contro
Can I just chime in here as a newbie Wine developer working on his
first patch and say that I find this kind of discussion invaluable? I've
lurked on wine-devel for a while and tried to gauge the answers to
these questions before, and personally bothered some of the devs
with a few questions that
On Mon, 2007-05-14 at 20:33 -0400, Ivan Gyurdiev wrote:
> > What Stefan says about discussing patches
> > is true--it helps if there's not a lot of debate around a patch.
> >
> This quote should go down in the history of open source :)
> I hope the word you're looking for is "controversy".
Ye
What Stefan says about discussing patches
is true--it helps if there's not a lot of debate around a patch.
This quote should go down in the history of open source :)
I hope the word you're looking for is "controversy".
On Mon, 2007-05-14 at 13:56 -0500, Tom Spear wrote:
Hey Tom,
> My last question is this: What is an acceptable amount of time I
> should wait before asking AJ what is wrong with a patch? I see that
> patches get submitted and then the next day they are committed
> oftentimes. However I would lik
> My last question is this: What is an acceptable amount of time I
> should wait before asking AJ what is wrong with a patch? I see that
> patches get submitted and then the next day they are committed
> oftentimes. However I would like I am pressuring him if I submit a
> patch, it didnt get com
On 5/14/07, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
Hi Tom!
I am afraid you have come accross an unmaintained part of wine. There is maybe
nobody who can competently help you. Nobody minds helping you, but nobody can
help you.
What happens then is that you write a mail and get no answers. You
Hi Tom!
I am afraid you have come accross an unmaintained part of wine. There is maybe
nobody who can competently help you. Nobody minds helping you, but nobody can
help you.
What happens then is that you write a mail and get no answers. You get
frustrated(not your fault), write a mail in which
Hi all, just wanted to know if anyone would _mind_ helping me with my
(small) todo list. I know I've been somewhat of an annoyance lately,
and for that I sincerely apologize. I'd really like to get the wine
uninstaller program up to speed with the patch I have been working on,
but it is not goin
Looking a bit more into the lstrcpyW and lstrcatW situation, the
reason it appears to be done is because if you add the slash directly
to PathUninstallW, then for some reason, the uninstaller shows no
entries, even when there are some.
Part of the reason I duplicated code in the original patch is
On 4/18/07, Detlef Riekenberg <[EMAIL PROTECTED]> wrote:
On Mo, 2007-04-16 at 16:44 -0500, Tom Spear wrote:
> I took lines 196-197 and duplicated that,
> changing HKEY_LOCAL_MACHINE to HKEY_CURRENT_USER, and
>
You can move most of the code from FetchUninstallInformation()
to a seperate function
On Mo, 2007-04-16 at 16:44 -0500, Tom Spear wrote:
> I took lines 196-197 and duplicated that,
> changing HKEY_LOCAL_MACHINE to HKEY_CURRENT_USER, and
>
You can move most of the code from FetchUninstallInformation()
to a seperate function and use the rootkey as Parameter.
get_uninstallinfo_fro
On 4/16/07, Briareos <[EMAIL PROTECTED]> wrote:
Am Montag, 16. April 2007 22:35 schrieb Tom Spear:
> I found a small bug in the uninstaller program, and would like to
> write the fix myself. I have a working copy in my local tree, but it
> duplicates code.
>
> Basically I found that uninstaller
Am Montag, 16. April 2007 22:35 schrieb Tom Spear:
> I found a small bug in the uninstaller program, and would like to
> write the fix myself. I have a working copy in my local tree, but it
> duplicates code.
>
> Basically I found that uninstaller does not scan the uninstall
> registry entry of HK
I found a small bug in the uninstaller program, and would like to
write the fix myself. I have a working copy in my local tree, but it
duplicates code.
Basically I found that uninstaller does not scan the uninstall
registry entry of HKEY_CURRENT_USER. I took lines 196-197 and
duplicated that, c
23 matches
Mail list logo
