This is the mail archive of the
mailing list for the GCC project.
Re: Repository for the conversion machinery
On Thu, Oct 6, 2016 at 1:19 PM, Eric S. Raymond <firstname.lastname@example.org> wrote:
> Joseph Myers <email@example.com>:
>> On Thu, 6 Oct 2016, Eric S. Raymond wrote:
>> > I thought the gcc conversion was done.
>> > I can make the repository available again if it's needed.
>> The conversion got stalled (I'm not sure why; maybe just Jason being busy
>> with other things) but is still intended (I'm not sure for when), so yes
>> the repository is still needed.
> I was unaware of this. I thought Jason had gotten the bit in his teeth
> and finished it while I was off doing other things.
After I ran into a couple of reposurgeon bugs and didn't hear back
from you, I started investigating rewriting the existing git svn
mirror with git filter-branch instead. That seems an attractive
option, but not long afterward I needed to shift focus to front end
development and decided to put off the conversion until the next stage
1. And here we are coming toward the end of that stage 1 and I
haven't found time for it yet, and am not likely to before the end of
this stage 1.
> (I'm sorry for not paying closer attention, but leading the project to fix NTP
> has eaten almost all my bandwidth for most of the last two years.)
> What do we do to get this restarted? I'll make the conversion-machinery
> repo visible again; what's the step after that?
As Joseph mentions, we should update the user map.
After that, I had a reposurgeon conversion of the website done apart
from the hooks, and could update that and put it in place as a good
prelude to converting the sources.
We should also reopen discussion of workflow and branch policies. One
concern I have about the git conversion is that gcc.gnu.org already
refuses git connections fairly frequently due to overloading, and I'm
afraid that will become much more common when current SVN users switch