similar to: [LLVMdev] Subversion Conversion Beginning

Basile STARYNKEVITCH wrote: > Dear All, > > according to http://llvm.org/SVNMigration.html the repository migrated to SubVersion (svn) > on june 5th 2007 (almost 10 days ago). > The migration was delayed. The subversion software was supposed to be configured this week by our IT department, but I have not heard from them yet. I've fired off an email to see what the status

On Fri, 2007-03-02 at 17:48 -0600, John Criswell wrote: > Dear All, > > I've just heard that there's been a recent discussion on the IRC channel > about moving the LLVM source repository from CVS to Subversion (SVN) and > that this migration may happen "soon." Yes, its been talked about for ages and its time to do it. We've debated the choice of repositories

All LLVM Developers: This is your notice that the LLVM project is converting from CVS to Subversion for its software repository. The conversion will happen on June 5th, 2007 unless otherwise notified. Please see http://llvm.org/SVNMigration.html for full details. We had hoped to have the conversion done by now, but a number of factors made it prudent for us to delay for a few more weeks. There

On Tue, 26 Jun 2007, Reid Spencer wrote: > I know we've cried wolf before, but the conversion of the LLVM projects' > software to use Subversion instead of CVS *WILL* occur on Friday June > 29th with the following approximate schedule: Great, I'm glad to see this happening. Thanks for making it happen. One request: when the change goes live, please make sure the various

Dear All, I've just heard that there's been a recent discussion on the IRC channel about moving the LLVM source repository from CVS to Subversion (SVN) and that this migration may happen "soon." Is such a migration being planned, and if so, what is the timeframe? How will the migration be performed? I and other LLVM users have deadlines in the near future, so we would like to

All, I know we've cried wolf before, but the conversion of the LLVM projects' software to use Subversion instead of CVS *WILL* occur on Friday June 29th with the following approximate schedule: * 09:00 CDT (14:00 UTC, 07:00 PDT) - CVS becomes read-only (commits prevented) * 09:05 CDT (14:05 UTC, 07:05 PDT) - Final conversion to SVN starts * 11:45 CDT

Dear LLVMers, The CVS to Subversion conversion that was originally scheduled for today will not be happening today. The reasons for this are: 1) There was a change of plans here at UIUC. Instead of hosting LLVM on the CS department SVN server as originally planned, we decided to host the server on the same machine as the llvm.org web site and the current CVS server. This was done to address

Dear All, according to http://llvm.org/SVNMigration.html the repository migrated to SubVersion (svn) on june 5th 2007 (almost 10 days ago). Did the migration happened as expected? http://llvm.org/releases/ still mention CVS, and nothing on http://llvm.org/docs/GettingStarted.html#checkout suggest to switch to svn instead of cvs. What is the current best way to download the latest snapshot:

The FreeBSD Project has begun the switch of its source code management system from CVS to Subversion. At this point in time, FreeBSD's developers are making changes to the base system in the Subversion repository. There is a replication system in place that exports our work to the legacy CVS tree on a continuous basis. People who are using our extensive CVS based distribution network

Everyone, We are at long last migrating the xiph.org source repository from to subversion. We've been wanting to do this for some years, but have been waiting for a conversion script that could deal with our creaky old cvs repository. Subversion, although perfectly usable for the past two years, recently announced a stable 1.0 release, and more importantly the major issues with the

Everyone, We are at long last migrating the xiph.org source repository from to subversion. We've been wanting to do this for some years, but have been waiting for a conversion script that could deal with our creaky old cvs repository. Subversion, although perfectly usable for the past two years, recently announced a stable 1.0 release, and more importantly the major issues with the

Everyone, We are at long last migrating the xiph.org source repository from to subversion. We've been wanting to do this for some years, but have been waiting for a conversion script that could deal with our creaky old cvs repository. Subversion, although perfectly usable for the past two years, recently announced a stable 1.0 release, and more importantly the major issues with the

Everyone, We are at long last migrating the xiph.org source repository from to subversion. We've been wanting to do this for some years, but have been waiting for a conversion script that could deal with our creaky old cvs repository. Subversion, although perfectly usable for the past two years, recently announced a stable 1.0 release, and more importantly the major issues with the

Dear LLVMers, The first phase of the Subversion conversion is complete. The CVS repository will no longer be available. You will now need to use the SVN server. Directions for getting LLVM from the SVN server can be found in the new Getting Started Guide (http://llvm.org/docs/GettingStarted.html). If you run a nightly tester, you should update your LLVM tree from SVN to get the new

Dear All, The CVS repository should now be read-only now. It should be safe to checkout files, but you should not be able to commit any changes (for safety, please don't try). We expect the conversion to be done by noon CDT. I should have an update on the status by then. -- John T.

All, At 0900 CDT tomorrow (1400 UTC) the Subversion migration will begin. At that time, CVS will be put in read-only mode while the conversion to Subversion is made. We expect the Subversion repository to be up and running 3 hours later at about 1200 CDT, 1000 PDT, or 1700 UTC. If you haven't got your subversion client yet, please do so now. If you host a nightly test, please get the latest

The Asterisk development team is pleased to announce that we have migrated our project repositories and development processes over to the Subversion version control system! Effective immediately, the primary source code distribution point for Asterisk, Zaptel and other related projects (other than release tarballs of course) will be http://svn.digium.com. The actual SVN repositories are

Dear developers, thanks to Charles (Lepple) and ESR hard work, we are now able to finalize our migration from Subversion to Git, on Alioth. As of now, our Subversion repository on Alioth<https://alioth.debian.org/scm/?group_id=30602>is FROZEN! Any new svn commit may simply be discarded, so beware! Most active developers are currently using github, as a temporary mean. But if you have any

Important Announcement! The netfilter.org CVS server (pserver.netfilter.org) has been deprecated by the new subversion repository at svn.netfilter.org. More information about the subversion revision control system can be found at http://subversion.tigris.org/. Everybody has read-only access to the new subversion tree using either svn+http or svn+https. We do not provide the native svn protocol.

I've been wondering if we should consider migrating from CVS to Subversion (aka SVN) for version control. There's a utility (cvs2svn) to convert a CVS repository while keeping full history. And SVN is supported by viewcvs (as used by http://cvs.xapian.org/) The main motivations are: * CVS doesn't really handle renaming files well. Either you "cvs rm" then "cvs