[Ffmpeg-devel] libswscale merged into the FFmpeg repository

[Rich Felker]

On Thu, Jul 27, 2006 at 11:12:42PM +0200, Michael Niedermayer wrote:
> > > There's always the possibility of just moving libswscale without
> > > history.  Given that the history is readily available in the MPlayer
> > > repository I don't think this is such a bad option.
> > 
> > So what's it going to be?  
> 
> its not possible to move libswscale from the mplayer repository to the
> ffmpeg repository while preserving history completly and consistently,
> svn does not support this so the only solution is to leave libswscale 
> in mplayers repository or create a new repository which of course would
> be alot of work for everyone and which would cause some troubble for
> everyone who has a modified ffmpeg source tree ...
> 
> for the case of a new repository we could
> A. switch back to cvs (all problems solved except that roots at mphq will
>    kill me)

That means everyone in the world will kill you, since with insecure
cvs crap everyone in the world might as well have root on mphq...

> B. put mplayer and ffmpeg in a single repository so moves become possible

Don't like.

> C. switch to some entirely different version control system

Don't like.

> D. just fix this single move and goto 1 for the next time we want to move
>    something

Probably best option. I don't see this as being a common occurrance.

> so my awnser here is again, leave it in mplayer, let ffmpeg check it out as
> external, the alternative

Even better.

> > I vote for moving libswscale without history.
> > It shouldn't be a great inconvenience, the history is available in the
> > MPlayer repository...
> 
> i will not accept that the history is "lost", even with cvs we where able
> to preserve it, and no, being available somewhere else is as good as lost
> svn annotate, svn log, svn up with a date none will work,
> actually nothing will work ...
> what you suggest is like cvs add and cvs remove, thats 2 steps back

Agree.

Rich