Wine uses an Open Source, open process development model.
Anyone may get the code, post opinions on what should be done,
and contribute patches. You will need to know C and/or perl, and something
about Unix and Windows.
Git is a fast directory
content manager, originally written for use with large repositories,
such as the Linux Kernel source.
You will need Git 1.3.1 or above.
Read the sections below on how to use our Git tree or check the
GitWine guide on the Wine Wiki.
A quick way to clean up your tree after you've been modifying
it and want to remove changes you haven't checked in is this:
cd wine
git diff-index -p HEAD > total-x.x.x.diff
patch -p1 -R < total-x.x.x.diff
git reset
Using the current x.x.x tags, you can keep a history of changes
that were in your Wine tree.
If you have made commits to the tree, and want to remove them all,
you can use the following more dangerous command:
git reset --hard origin
This will wipe out any local changes you have made, so use it with caution.
Staying Up-To-Date
First, make sure to clean your tree as described above, then
run the following commands from the top level wine directory:
git fetch
git rebase origin
Source Tree Browsing via the Web
The source code of the entire Wine tree is (LXR-based)
cross-referenced and available for browsing, including a search engine.
This cross-references source is based on the snapshot-releases and is made available at:
The documentation lives in a separate CVS tree on Sourceforge.
To get a git repository of the documentation create a new directory and
in a terminal run in that directory:
