similar to: [LLVMdev] Subversion Conversion Running

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

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

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

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:

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

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

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

Since there was some interest in checking out Subversion and seeing if it might be helpful to the LLVM project, I went ahead and created Subversion repositories from the current CVS tree. The content of these repositories can be seen at: http://toolchain.org/websvn/ and are current as of roughly 23:03 UTC, 15 Mar 2005 (more or less). There are copies of LLVM itself, the CFE, the llvm-test

Dear LLVMers, The configuration of the subversion software is still incomplete, so we will not be starting the switch over to SVN at 1:00 pm CDT today as planned. I do not know yet when the conversion can be rescheduled. It looks like tomorrow (Tuesday) is the earliest that we can begin the conversion. I'll keep the list updated as I learn more details. -- John T.

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 All, The Siebel Center (the building in which the llvm.org server is housed) is undergoing some significant work on its cooling system this weekend. Air conditioning will not be available, so we have been advised to shut down systems until the cooling work is done. This outage affects the following LLVM services: 1) The LLVM web server and SVN server will be unavailable starting noon

Dear All, The Subversion Migration is beginning now. CVS commit access will be disabled. -- John T.

Hi, I'd just like to point out that Speex recently switched to Subversion and that the anonymous checkout is now: svn co http://svn.xiph.org/trunk/speex/ While the anonymous CVS still works, it is no longer being updated, so you should stop using it. Jean-Marc -- Jean-Marc Valin http://www.xiph.org/~jm/ LABORIUS Université de Sherbrooke, Québec, Canada -------------- next part

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

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

Hello, I'm working at a web-development company and I wanted to use samba as a central fileserver. Most client-computers use linux and osX, but there are some windows PC's on the network also. We use subversion as a central repository and (until now) all developers had to checkout their working copies to their own machines. Since we mostly use Ruby on Rails for development, this means

Hello, I don't know is this a Samba or Subversion (or my faulty config) related issue so I'll start here. I'd like to clarify that the need to have just one working copy (and not one per user on his/her local disk) is vital here. My situation: - CentOS6, - Active Directory-enabled environment - Server is connected to AD, users are synced up - All users are in AD group

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've just encountered an issue where using --link-dest from within a Subversion working copy does not create hard links as intended. The idea is to supply the build toolchain for an embedded software development project to all users without having to force everybody to check out the whole stuff. This way we have the toolchain under

Dear All, I need one or more volunteers to try out their nightly testers with the -usesvn option. We're not running on here at the University of Illinois regularly, so if someone could try one of theirs out before tomorrow 9:00 am CDT, I'd be very appreciative. Thanks. -- John T.

I have a project under Subversion, deployed by Capistrano. When it is deployed, obviously I need to deploy "real" copies of database.yml, deploy.rb, and maybe a couple of other files. But if I offer it for public checkout, I obviously do not want these files as part of the checked out code. What''s the best way to handle this? --Al Evans -- Posted via