[MPlayer-DOCS] DOCS/tech/cvs-howto.txt

[Ivo]

On Thursday 22 June 2006 00:32, Ivo wrote:
> I didn't got to writing something today, but I will try to come up with a
> short version of section III tomorrow. Something describing a typical
> development procedure, like checkout, edit, create patch, send patch to
> mailinglist, fix, etc, commit. We could decide later what to do with it.
> Like replace section III, add it to section I, or just bin it ;)

See attachment.

--Ivo
-------------- next part --------------
III. Beginners Guide
====================

The typical flow of development would be:

1. Checkout the source:

    svn checkout svn://svn.mplayerhq.hu/mplayer/trunk/

2. Make your changes

3. Create a patch:

  Run svn diff from the source of the svn tree, like this:

    svn diff > my_changes.patch

  If you have made several changes, but only want to submit one for review
  by other developers, you can specify the filename(s), for example:

    svn diff mplayer.c > major_cleanup.patch

4. Check the patch:

  Checkout another, clean svn source tree and verify your patch:

    patch -p1 --dry-run < my_changes.patch

  If there are no errors, you can apply your patch:

    patch -p1 < my_changes.patch

  After that, verify that MPlayer still builds correctly with your patch
  applied.

5. Submit the patch:

  Send an e-mail to the mplayer-dev-eng mailinglist. Describe what your
  patch does and why and attach the patch file for review by others.

6. During the review process, incorporate all suggested fixes. Go to step 2
  repeatedly until there is nothing more to do for step 6. Offcourse, if
  you don't agree with certain suggestions, things can be discussed on
  the mailinglist in a polite manner.

7. Commit the patch:

  If your patch is accepted, commit with:

    svn commit filename(s)

  Go to step 2 ad infinitum until MPlayer is the perfect Media Player ;)

Note: If you are listed as the maintainer for a particular piece of code,
you can skip step 5 and 6 if your patch _only_ applies to the code you
maintain. If it touches other code or is otherwise very intrusive, please
post it to mplayer-dev-eng first.