[MPlayer-dev-eng] [PATCH] A/V sync improvement for TV streams
Laurent
laurent.aml at gmail.com
Mon Oct 27 15:16:47 CET 2008
On 10/27/08, Michael Niedermayer <michaelni at gmx.at> wrote:
> On Sun, Oct 26, 2008 at 04:01:57PM +0200, Uoti Urpala wrote:
> > On Mon, 2008-10-20 at 19:23 -0400, Laurent wrote:
> > I think it's a bad idea to try porting random individual changes from
> > the git tree to svn.
>
> I think its a good idea to back port good changes from forks to the main
> tree, after all we (or at least i) want the main tree to have many
> features and few bugs. And of course we might one day switch the main tree
> to git. But that does not mean that this will be in any way related to your
> personal fork.
>
>
> > If you start doing that exactly which ones would
> > they be?
>
> all good ones i guess, thats the idea of porting individual changes.
>
>
> > Applying patches like this to svn would cause extra work when
> > merging svn changes (it'd conflict with the corresponding code already
> > in git).
>
> Well, i guess if you fork something you should live with the fact
> that some of your changes are going to be merged back by other people.
> If thats too much work you shouldnt have forked.
>
>
> > If you need some functionality from the git tree I think the
> > effort is better spent on making the git version work for you if it
> > doesn't already.
>
> I cannot speak for others but i have no interrest in your personal fork.
> If i do have time and motivation to work on mplayer that will be spend
> on the main tree or in case something happens to mplayer at mphq a fork from
> that which is ruled by the community of developers who work on it.
>
I agree with Michael, for all points.
I have no interrest in working in this GIT fork, nor in any other's fork.
I've been using MPlayer for years and never heard of this GIT
repository before joining the mailing lists. 99% of MPlayer users
would be in this case.
My interrest is to use my time (and reviewer's) for this whole community.
If your patch would have been applied upstream before, it might have
spare hours of troubleshooting to a few of us (and definitely me, at
least).
Thanks,
Laurent
More information about the MPlayer-dev-eng
mailing list