[MPlayer-dev-eng] PATCHES

[seru]

Arpi himself said 5 months ago:

> Anyway, imho we've reached that point where we should switch from mailling
> list to some patch management system. I don't kno any, so i'm asking about
> your experiences... lets'tell me what is possible and which project is to go
> with.

> my ideas about the ideal patch management system:
> - user commits his patch, through some web interface, or via email, along
> with his comments. it also arrives in form of mail to -dev-eng or new list
> mplayer-patches by the patch management system so we can discuss it
> - you can assign the patch to somebody (mplayer developers with cvs access)
> for review - optionaly more than one person - optionaly it does this
> automatically depending on area (selected by patch maker) the patch belongs
> to
> - you can set priority for patch, and view them sorted by it
> - you can refuse or accept patch, not listed any more by default
> - user can commit updated version of his patch, without re-creating teh
> patch entry, so we can follow the changes of the patch (diff of diff? :))"

Bugzilla does all this (see http://www.mplayerhq.hu/pipermail/mplayer-dev-eng/2002-July/009958.html ) How about installing it? 
Would be perfect for both bug reports and sending patches.
ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1.tar.gz to download :)

And talking about installing new software, what about subversion?