[Ffmpeg-devel] libswscale merged into the FFmpeg repository

[Uoti Urpala]

On Thu, 2006-07-27 at 23:12 +0200, Michael Niedermayer wrote:
> On Thu, Jul 27, 2006 at 06:14:50PM +0200, Diego Biurrun wrote:
> > 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

cvs was able to preserve the file-specific changes but not the
repository state in a way that would have allowed checking out old
versions etc.

> , and no, being available somewhere else is as good as lost

Exaggeration.

> svn annotate, svn log, svn up with a date none will work,
> actually nothing will work ...

annotate:
After moving without history, would require one more step to check the
other repository for changes older than the move. So this is negative
for moving without history, but nothing as bad as "as good as lost".

log:
Per-file log would be split at move, again requiring an extra step for
entries older than move. Global log would work better after moving, as
the entries would appear in the right repository, and would have correct
information about which files were committed together (committing
externals would make everything appear as independent changes).

svn up with a date:
Would work correctly. Without moving it will NOT work for any date after
the external is added. If the entry in the ffmpeg repository says "check
out the latest libswscale here", it will say "latest" whatever revision
of ffmpeg you check out. So this works much worse with externals. It
might be possible to work around it with hacks that make the external
definition versioned and then automatically commit changes to ffmpeg
changing the versioning whenever something in libswscale changes.

Externals aren't really meant as a replacement for moving files or
directories, they're meant as a replacement for telling people "copy
version X of library Y here".