CVS write access users should give the subversion setup a try this week. Directions on how to do common operations are at http://gcc.gnu.org/wiki/SvnHelp
I have placed the repo in exactly the place on gcc.gnu.org it will end up in during the final conversion, and in the exact condition (IE tags, branches, etc) it will be in when we convert, minus the changes over the next week I have converted the update_version script in maintainer-scripts and checked it in under the name update_version_svn I tested it from the gccadmin account on gcc.gnu.org, as well as remotely (while the old update_version pretends to support remote updating, it doesn't). Note that this is a pretty straightforward conversion, but the whole script is really overkill for the following reason: We can now identify the exact version of gcc t have simply by the revision number and branch name. So maintaining all this stuff in a DATESTAMP, etc, is severe overkill when you could simply use the result of "svnversion .' and commit that to a file, or do it client side). see http://svnbook.red-bean.com/en/1.1/re57.html for more details on the output of svnversion. I will finish updating the gcc_release script today. The other contrib scripts have been updated by Ben Elliston, and were posted to gcc-patches. --Dan
