[Ffmpeg-devel] switch to svn
Stepping, Michael Web.de
Mon Oct 24 17:21:00 CEST 2005
my five cents on experience with svn:
biggest disadvantage is:
$Log is not supported, only $ID which reflects
the latest change. But in ffmpeg project it does not count neither, nobody (looks
like) uses this comfortable element of version history.
Additionally, the "rename" function is not really a "rename". It is a
"delete" and consecutive "add". The history of the file is interrupted.
Another disadvantage is the lack of "sharing" files or directories.
Configurations are done on client side like keyword expansion, adding attributes
and some others and are not server centric administerable.
The statements above are valid for TortoiseSVN 1.1 till 1.2.4 which relys on the
adequate svn version.
Some of my statements are possibly the same for CVS, I do not know.
Usually I use VSS (with those specific disadvantages).
PS: Sorry, I am used since years to do top-post. Forgive me.
> -----Original Message-----
> From: ffmpeg-devel-bounces at mplayerhq.hu
> [mailto:ffmpeg-devel-bounces at mplayerhq.hu]On Behalf Of Mike Melanson
> Sent: Thursday, October 20, 2005 5:07 PM
> To: FFMpeg development discussions and patches
> Subject: Re: [Ffmpeg-devel] switch to svn
> Attila Kinali wrote:
> > Hi,
> > I would like to ask whether the developers of FFmpeg and MPlayer
> > would agree to switch from cvs to svn.
> > The reason is that svn would allow to more easily seperate
> > the repo users from system users and thus make administration
> > simpler. It also has IMHO better support for backups and
> > a few other nice to have features.
> >>From a user point of view, the change would mostly just
> > require to use svn instead of cvs with nearly all commands
> > being the same.
> > So, would you agree on the switch from cvs to svn?
> No objections.
> -Mike Melanson
> ffmpeg-devel mailing list
> ffmpeg-devel at mplayerhq.hu
More information about the ffmpeg-devel