Re: New SVN repo is up
On Tue, 22 Nov 2005, Gabriel Dos Reis wrote: > | I've merged the gcc_update change to 4.0 branch, 3.4 branch and > > Did you mean that gcc_release on those branches is now using SVN? > That does not seem to be the case. It's gcc_update I merged, not gcc_release. The main pre-SVN differences between gcc_release in the branches should have been the details of which files with version number / date / release status get updated. -- Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/ [EMAIL PROTECTED] (personal mail) [EMAIL PROTECTED] (CodeSourcery mail) [EMAIL PROTECTED] (Bugzilla assignments and CCs)
Re: New SVN repo is up
Daniel Berlin <[EMAIL PROTECTED]> writes: | On Tue, 2005-11-22 at 16:51 +0100, Gabriel Dos Reis wrote: | > "Joseph S. Myers" <[EMAIL PROTECTED]> writes: | > | > | On Fri, 28 Oct 2005, Daniel Berlin wrote: | > | | > | > contrib/ scripts have been updated in the new repository | > | | > | I've merged the gcc_update change to 4.0 branch, 3.4 branch and | > | > Did you mean that gcc_release on those branches is now using SVN? | No, I don't remember whether the new gcc_release was copied onto those | branches. Thanks. I tried to update gcc_release on gcc-3_4-branch but currently it is a complete failure (see my other message). -- Gaby
Re: New SVN repo is up
On Tue, 2005-11-22 at 16:51 +0100, Gabriel Dos Reis wrote: > "Joseph S. Myers" <[EMAIL PROTECTED]> writes: > > | On Fri, 28 Oct 2005, Daniel Berlin wrote: > | > | > contrib/ scripts have been updated in the new repository > | > | I've merged the gcc_update change to 4.0 branch, 3.4 branch and > > Did you mean that gcc_release on those branches is now using SVN? No, I don't remember whether the new gcc_release was copied onto those branches. > That does not seem to be the case. > > -- Gaby
Re: New SVN repo is up
"Joseph S. Myers" <[EMAIL PROTECTED]> writes: | On Fri, 28 Oct 2005, Daniel Berlin wrote: | | > contrib/ scripts have been updated in the new repository | | I've merged the gcc_update change to 4.0 branch, 3.4 branch and Did you mean that gcc_release on those branches is now using SVN? That does not seem to be the case. -- Gaby
Re: New SVN repo is up
Daniel Berlin wrote: > [ Mark, my emails to gcc-announce are dropped on the floor, can you > forward this there? ] I've posted a slightly more user-centric announcement. I hope that's OK. Thanks, -- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304
Re: New SVN repo is up
Joseph S. Myers wrote: > On Fri, 28 Oct 2005, Daniel Berlin wrote: > > >>contrib/ scripts have been updated in the new repository > > > I've merged the gcc_update change to 4.0 branch, 3.4 branch and > csl-arm-branch. In so doing, bug 20731 is fixed since the branch name is > no longer hardcoded. I have therefore also applied the following patch to > branching.html to remove mention of updating gcc_update. Swell! Thanks, -- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304
Re: New SVN repo is up
On Fri, 28 Oct 2005, Daniel Berlin wrote: > contrib/ scripts have been updated in the new repository I've merged the gcc_update change to 4.0 branch, 3.4 branch and csl-arm-branch. In so doing, bug 20731 is fixed since the branch name is no longer hardcoded. I have therefore also applied the following patch to branching.html to remove mention of updating gcc_update. Index: branching.html === RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v retrieving revision 1.20 diff -u -r1.20 branching.html --- branching.html 23 Mar 2005 17:30:13 - 1.20 +++ branching.html 28 Oct 2005 17:12:18 - @@ -26,10 +26,6 @@ Update the file gcc/BASE-VER on the mainline, to use the next major release number (e.g., 3.2 instead of 3.1). -Update the file gcc/contrib/gcc_update on the branch, -so that the "$GCC_CVS update" invocation uses -"-r BRANCH_NAME". - Create a new htdocs/gcc-VERSION directory for the next major release in the wwwdocs repository and populate it with initial copies of changes.html and -- Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/ [EMAIL PROTECTED] (personal mail) [EMAIL PROTECTED] (CodeSourcery mail) [EMAIL PROTECTED] (Bugzilla assignments and CCs)
RE: New SVN repo is up
On Fri, 2005-10-28 at 18:25 +0100, Dave Korn wrote: > Mike Stump wrote: > > On Oct 28, 2005, at 9:20 AM, Dave Korn wrote: > >> snip > >> [EMAIL PROTECTED] /gnu/HEAD> svn co svn+ssh://[EMAIL PROTECTED]/svn/gcc/ > >> trunk > >> Enter passphrase for key '/home/dk/.ssh/id_rsa': > >> > >> [ 40 minutes later, no response and still waiting ] > >> snip > > > > Takes around 1360 seconds... Switching that to 4.0 trunk takes 691 > > seconds... > > > Hmm. It still wasn't doing anything, so I killed it (after about 1hr 40m, > total). An anonymous checkout works fine. > > I might try an earlier version (from the official cygwin package) and see if > that behaves any differently. Maybe I just didn't find all the necessary > configure options when I compiled it. (Let's remove mark from the cc list :P) Any problems network wise are generally in APR. SVN doesn't do sockets on it's own, we rely completely on APR to provide sane implementations :)
Re: New SVN repo is up
On Fri, 2005-10-28 at 09:45 -0700, Mike Stump wrote: > On Oct 28, 2005, at 9:20 AM, Dave Korn wrote: > > snip > > [EMAIL PROTECTED] /gnu/HEAD> svn co svn+ssh://[EMAIL PROTECTED]/svn/gcc/ > > trunk > > Enter passphrase for key '/home/dk/.ssh/id_rsa': > > > > [ 40 minutes later, no response and still waiting ] > > snip > > Takes around 1360 seconds... Switching that to 4.0 trunk takes 691 > seconds... > There are like 80 billion people trying to update at the moment :)
RE: New SVN repo is up
Mike Stump wrote: > On Oct 28, 2005, at 9:20 AM, Dave Korn wrote: >> snip >> [EMAIL PROTECTED] /gnu/HEAD> svn co svn+ssh://[EMAIL PROTECTED]/svn/gcc/ >> trunk >> Enter passphrase for key '/home/dk/.ssh/id_rsa': >> >> [ 40 minutes later, no response and still waiting ] >> snip > > Takes around 1360 seconds... Switching that to 4.0 trunk takes 691 > seconds... Hmm. It still wasn't doing anything, so I killed it (after about 1hr 40m, total). An anonymous checkout works fine. I might try an earlier version (from the official cygwin package) and see if that behaves any differently. Maybe I just didn't find all the necessary configure options when I compiled it. cheers, DaveK -- Can't think of a witty .sigline today
Re: New SVN repo is up
On Fri, 2005-10-28 at 19:22 +0200, Andreas Schwab wrote: > Daniel Berlin <[EMAIL PROTECTED]> writes: > > > contrib/ scripts have been updated in the new repository > > It appears this happend only on the trunk. > Yes. I will udpate them on branches as well. > Andreas. >
Re: New SVN repo is up
Daniel Berlin <[EMAIL PROTECTED]> writes: > contrib/ scripts have been updated in the new repository It appears this happend only on the trunk. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Re: New SVN repo is up
On Oct 28, 2005, at 9:20 AM, Dave Korn wrote: snip [EMAIL PROTECTED] /gnu/HEAD> svn co svn+ssh://[EMAIL PROTECTED]/svn/gcc/ trunk Enter passphrase for key '/home/dk/.ssh/id_rsa': [ 40 minutes later, no response and still waiting ] snip Takes around 1360 seconds... Switching that to 4.0 trunk takes 691 seconds...
Re: New SVN repo is up
> Should I assume that the reason that my attempt to "svn co" the > repository for the first time is that the repository is massively > overloaded due to everyone on the list hitting it at the same time? Mine started right away. Checkout proceeding normally.
RE: New SVN repo is up
Daniel Berlin wrote: > [ Mark, my emails to gcc-announce are dropped on the floor, can you > forward this there? ] > > The new SVN repository is up. snip [EMAIL PROTECTED] /gnu/HEAD> svn co svn+ssh://[EMAIL PROTECTED]/svn/gcc/trunk Enter passphrase for key '/home/dk/.ssh/id_rsa': [ 40 minutes later, no response and still waiting ] snip Should I assume that the reason that my attempt to "svn co" the repository for the first time is that the repository is massively overloaded due to everyone on the list hitting it at the same time? cheers, DaveK -- Can't think of a witty .sigline today
New SVN repo is up
[ Mark, my emails to gcc-announce are dropped on the floor, can you forward this there? ] The new SVN repository is up. I will rescript the cvs sessions in wwwdocs, and post the final set of wwwdocs changes. contrib/ scripts have been updated in the new repository maintainer-scripts/ have as well, excluding gcc_release, which i am still testing but will post in the next few hours. I will create and place starting tarballs for svk repos for people who want them (this will take a day or so to generate). --Dan
