version control system moved to Subversion

[Sam Hocevar]

Hello! This is our next step towards total world domination, namely
the utter eradication of CVS in favour of SVN (Subversion). As of now,
only libdvbpsi, libdvdcss and libdvdplay have been moved, because their
developer count was low enough to ensure a painless transition.

The new repositories are available at the following SVN addresses:

svn://svn.videolan.org/libdvbpsi/
svn://svn.videolan.org/libdvdcss/
svn://svn.videolan.org/libdvdplay/

HEAD is in trunk/, branches are in branches/ and tags are in tags/,
which means that the latest version can be retrieved this way for
instance:

svn co svn://svn.videolan.org/libdvdcss/trunk libdvdcss_HEAD

Here is a quick FAQ:

Q. SVN? WTF!
A. Subversion (svn) is a powerful replacement for CVS. See the website
at http://subversion.tigris.org/

Q. I was not using CVS, what should I do?
A. Nothing. This change will not affect you at all.

Q. I was using CVS in read-only mode, what should I do?
A. Nothing. Scripts have been set up that replicate all SVN changes to
HEAD into the CVS tree every ten minutes, so that anonymous CVS users
will not suffer any change.

Q. I was a CVS commiter, what should I do?
A. Learn how to use Subversion first, and send me a new plaintext
password so that I can create your SVN account. Scrambled passwords and
encrypted connections are not available yet.

Q. I was a CVS commiter, and I had pending changes!
A. Don't worry. Use "cvs diff" to generate a patch of your local
changes, then checkout a new tree from the SVN repository, and apply
your patch to this new checkout.

Q. I am a {vlc|vls|whatever} commiter, should I start learning SVN?
A. Yes. Eventually all VideoLAN repositories will be moved to SVN. But
due to the high number of VLC commiters, this is likely to take more
time until everyone can use Subversion on their favourite OS. A survey
will be conducted before anything is attempted.

Please report any problems to me.

Have fun,

[Sam Hocevar]

Hello! This is our next step towards total world domination, namely
the utter eradication of CVS in favour of SVN (Subversion). As of now,
only libdvbpsi, libdvdcss and libdvdplay have been moved, because their
developer count was low enough to ensure a painless transition.

The new repositories are available at the following SVN addresses:

svn://svn.videolan.org/libdvbpsi/
svn://svn.videolan.org/libdvdcss/
svn://svn.videolan.org/libdvdplay/

HEAD is in trunk/, branches are in branches/ and tags are in tags/,
which means that the latest version can be retrieved this way for
instance:

svn co svn://svn.videolan.org/libdvdcss/trunk libdvdcss_HEAD

Here is a quick FAQ:

Q. SVN? WTF!
A. Subversion (svn) is a powerful replacement for CVS. See the website
at http://subversion.tigris.org/

Q. I was not using CVS, what should I do?
A. Nothing. This change will not affect you at all.

Q. I was using CVS in read-only mode, what should I do?
A. Nothing. Scripts have been set up that replicate all SVN changes to
HEAD into the CVS tree every ten minutes, so that anonymous CVS users
will not suffer any change.

Q. I was a CVS commiter, what should I do?
A. Learn how to use Subversion first, and send me a new plaintext
password so that I can create your SVN account. Scrambled passwords and
encrypted connections are not available yet.

Q. I was a CVS commiter, and I had pending changes!
A. Don't worry. Use "cvs diff" to generate a patch of your local
changes, then checkout a new tree from the SVN repository, and apply
your patch to this new checkout.

Q. I am a {vlc|vls|whatever} commiter, should I start learning SVN?
A. Yes. Eventually all VideoLAN repositories will be moved to SVN. But
due to the high number of VLC commiters, this is likely to take more
time until everyone can use Subversion on their favourite OS. A survey
will be conducted before anything is attempted.

Please report any problems to me.

Have fun,

[Sam Hocevar]

Hello! This is our next step towards total world domination, namely
the utter eradication of CVS in favour of SVN (Subversion). As of now,
only libdvbpsi, libdvdcss and libdvdplay have been moved, because their
developer count was low enough to ensure a painless transition.

The new repositories are available at the following SVN addresses:

svn://svn.videolan.org/libdvbpsi/
svn://svn.videolan.org/libdvdcss/
svn://svn.videolan.org/libdvdplay/

HEAD is in trunk/, branches are in branches/ and tags are in tags/,
which means that the latest version can be retrieved this way for
instance:

svn co svn://svn.videolan.org/libdvdcss/trunk libdvdcss_HEAD

Here is a quick FAQ:

Q. SVN? WTF!
A. Subversion (svn) is a powerful replacement for CVS. See the website
at http://subversion.tigris.org/

Q. I was not using CVS, what should I do?
A. Nothing. This change will not affect you at all.

Q. I was using CVS in read-only mode, what should I do?
A. Nothing. Scripts have been set up that replicate all SVN changes to
HEAD into the CVS tree every ten minutes, so that anonymous CVS users
will not suffer any change.

Q. I was a CVS commiter, what should I do?
A. Learn how to use Subversion first, and send me a new plaintext
password so that I can create your SVN account. Scrambled passwords and
encrypted connections are not available yet.

Q. I was a CVS commiter, and I had pending changes!
A. Don't worry. Use "cvs diff" to generate a patch of your local
changes, then checkout a new tree from the SVN repository, and apply
your patch to this new checkout.

Q. I am a {vlc|vls|whatever} commiter, should I start learning SVN?
A. Yes. Eventually all VideoLAN repositories will be moved to SVN. But
due to the high number of VLC commiters, this is likely to take more
time until everyone can use Subversion on their favourite OS. A survey
will be conducted before anything is attempted.

Please report any problems to me.

Have fun,

[Jean-Paul Saman]

Sam,

Which version of the Subversion do we use 1.0 I assume?

Post by Sam Hocevar
svn://svn.videolan.org/libdvbpsi/
svn://svn.videolan.org/libdvdcss/
svn://svn.videolan.org/libdvdplay/
Please report any problems to me.

Wouldn't it be safer to use svn+ssh://svn.videolan.org/libdvbpsi/ ?? So
that our passwords won't travel in clear text?
And how do we sent our passwords safe to you?? I mean not in clear text
e-mail?
--
Many greetings,
Jean-Paul Saman

Consultant
--------------------------------------------------------------
VLC iPAQ maintainer http://www.videolan.org
RedHat Certified Engineer RHCE number: 807202745005548
--------------------------------------------------------------

[Sam Hocevar]

Post by Jean-Paul Saman
Which version of the Subversion do we use 1.0 I assume?

The server still uses 0.37 but will move to 1.0 as soon as possible;
clients are compatible across revisions, you need not have the same
version as on the server.

Post by Jean-Paul Saman
Wouldn't it be safer to use svn+ssh://svn.videolan.org/libdvbpsi/ ?? So
that our passwords won't travel in clear text?

Yes it would be safer. However that would require the creation of
Unix accounts on the server, and I do not want that. I will set up
SVN-SSL later.

Post by Jean-Paul Saman
And how do we sent our passwords safe to you?? I mean not in clear text
e-mail?

You can PGP-encrypt it (my key's fingerprint is 1155 4B19 A50F 1136
6E60 A499 7CF3 F5AF 2949 9F61). But honestly it's not such a big deal.