I have several spare evening on my hands and I want to help the wine
development effort. I have read a lot of the documentation and have decided
to help document the API. I have obtained a copy of the last snap shot and
compiled it (with a change of the prefix variable in the configure script to
/opt/wine). I have run several winnt programs and had fair success. Since
I want to help, am a native speaker of English, and have access to a fair
amount of documentation on the windows API, and will be reading to code
anyway I thought I would start by expanding the API documentation in line
with http://www.winehq.com/Docs/wine-devel/documentation.shtml#API-DOCS
<http://www.winehq.com/Docs/wine-devel/documentation.shtml#API-DOCS> .
My problem is that during these few spare evenings my access to the internet
is via a firewall that does not have a hole for port 2401 and I am unlikely
to be able to get a hole added for this port hence I cannot access the cvs
tree directly. This makes submitting patches tricky. Some ideas I have had
include
Obtaining a copy of the full cvs tree pointing the CVSROOT at this tree and
continuing as normal. I would update the local cvs tree each time a new
snapshot is issued. I have tried this but I am having trouble getting a
copy of the whole cvs tree. (Something is blocking anonymous ftp access).
Duplicating the snapshot tree locally and generating diff against the
unmodified tree when submitting patches. For instance if the snap shot is
wine-20001202 and I put work in wine then diff -ru wine-20001202 wine should
produce something relatively close to what one would get from cvs. The
problem is that it is still not easy to apply.
Can the patch program work in place with only a minor command line change?.
For instance if I were to get a fresh snapshot move it to some directory say
wine-cvs, get a copy of the latest version of the file that I want to add
documentation to, copy it into wine-cvs, run the diff from my working
directory then edit out the reference in the
Diff preamble to wine-cvs, would it be better. For example
/otp/wine - working directory
/wine-cvs - snapshot with partial manual update from current cvs
>From in /opt/wine execute
diff -ru ../wine-cvs .
edit the resulting
diff -ru ../wine-cvs/dlls/kernel/comm.c dlls/kernel/comm.c
--- ../wine-cvs/dlls/kernel/comm.c Fri Dec 1 18:58:28 2000
+++ ./dlls/kernel/comm.c Mon Dec 18 21:28:52 2000
@@ -1489,17 +1489,37 @@
to
diff -ru ../wine-cvs/dlls/kernel/comm.c dlls/kernel/comm.c
--- ./dlls/kernel/comm.c Fri Dec 1 18:58:28 2000
+++ ./dlls/kernel/comm.c Mon Dec 18 21:28:52 2000
@@ -1489,17 +1489,37 @@
Would it produce something as easy to apply as a normal cvs diff patch?
Does anyone have any better ideas or any suggestions on how to proceed?
Andrew.
