Hi, On Wed, 2019-12-18 at 21:55 +0000, Joseph Myers wrote: > On Tue, 17 Dec 2019, Joseph Myers wrote: > > I've made test conversions of the GCC repository with reposurgeon > > available (gcc.gnu.org / sourceware.org account required to access > > these git+ssh repositories, it doesn't need to be one in the gcc group > > or to have shell access). More information about the repositories, > > conversion choices made and known issues is given below, and, as noted > > there, I'm running another conversion now with fixes for some of those > > issues and the remaining listed issues not fixed in that conversion > > are being actively worked on. > > > > git+ssh://gcc.gnu.org/home/gccadmin/gcc-reposurgeon-1a.git > > git+ssh://gcc.gnu.org/home/gccadmin/gcc-reposurgeon-1b.git > > There are now four more repositories available. > > git+ssh://gcc.gnu.org/home/gccadmin/gcc-reposurgeon-2a.git > git+ssh://gcc.gnu.org/home/gccadmin/gcc-reposurgeon-2b.git > git+ssh://gcc.gnu.org/home/gccadmin/gcc-reposurgeon-3a.git > git+ssh://gcc.gnu.org/home/gccadmin/gcc-reposurgeon-3b.git
For those without gcc.gnu.org accounts I made mirrors at: https://code.wildebeest.org/git/gcc/ There is also a mirror of Maxim's gcc-reparent branch: https://code.wildebeest.org/git/gcc/gcc-reparent/ And the traditional gcc git-svn mirror: https://code.wildebeest.org/git/mirror/gcc/ The last two seem to be kept up to date with current svn. Cloning should work through both git:// and (smart) https:// protocols. Please be gentle. This is on a little machine in my basement. Each full clone also takes 1GB+ of data. So you might just want to look at them just through the cgit webinterface. But hopefully it is still useful. I will likely delete these again after we have picked a conversion we actually want to use. Do we already have a new date for when we are making that decision? Thanks, Mark
