[MPlayer-dev-eng] [PATCH] libbs2b audio filter
Andrew Savchenko
bircoph at gmail.com
Tue Mar 24 20:38:01 CET 2009
Hi,
On Tuesday 24 March 2009 03:31, Uoti Urpala wrote:
> On Mon, 2009-03-23 at 21:30 +0300, Andrew Savchenko wrote:
> > > I did add something like this (in the git repo).
> >
> > Then why this is not added to the main svn tree? This is very
> > good
>
> There's lots of such stuff in the git tree. Porting things to
> svn would be a waste of effort; moving the rest of development
> to the git tree is more practical.
Just curious, but is this common command decision? I haven't heard
about it. And if you have a lot of huge changes they will take a
long time to be approved by other developers. As I can see code QA
requirements are rather high here, this is good, but also this
implicates some responsibility for taking care about changes to be
approved.
Concerning git. If this will be an oficial decision, I'll follow.
But IMO git is overmuch for middle-size project like MPlayer. Git
suits good for large *and* distributed projects like kernel, but
for smaller tasks in may produce nothing but overhead. Yet again,
this is my private subjective point of view.
> > that someone cares about this issue, but it should be fixed
> > not only somewhere locally, but at the mainstream. What about
>
> The reason the git tree is not the "mainstream one" yet is that
> some changes are controversial and there are developers who
> still want to work on the svn tree.
Oh, please, do not try to fork. There is no good from this kind of
attempts, you may remember mplayer-xp (or -mp, I don't remember
exactly). If you have some changes, you must discuss them. I'm on
this lists for several years (thought I'm not rather active) and I
can see that most people are open for discussions here. Yes, you
need to spend some time, yes, rules are strict, but there is no
other way for collaborative work and stable code simultaneously.
> The git tree will become "mainstream" in the future however,
I doubt it, I remember some of this kind of statements in the past,
but not all of them were realized.
> and even if some old
> developers who dislike the new changes in git try to keep
> maintaining a separate svn-based version it's unlikely they
> could keep it competitive.
MPlayer, like many other OSS projects (and not only opensource)
somewhat lacks manpower in one degree or another. I do assume that
any kind of split/fork idea will bring zero to negative benefit to
everyone.
--
Best regards,
Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/attachments/20090324/0bf40c67/attachment.pgp>
More information about the MPlayer-dev-eng
mailing list