Re: So what's the status of the Git migration?
esr wrote: > [...] >> Another year; another release; and still no sign of progress on the git >> migration. > [...] > The current issue - and, I think, the last major one - is that there are > over 150 nid-branch deletes to be resolved. Is there a mandate that this conversion be Perfect? How harmful would it be to retain some ambiguity / imperfection in the resulting git repo, considering that the svn repo can stick around indefinitely as a historical reference? - FChE
Re: So what's the status of the Git migration?
Richard Earnshaw (lists) : > Another year; another release; and still no sign of progress on the git > migration. > > Any ideas on how much longer this is going to take? > > R. I'm still working on it. It's a slow process because the repo is so huge that full conversions take around 9 hours each, That means that on a good day I can test naybe two point changes. The current issue - and, I think, the last major one - is that there are over 150 nid-branch deletes to be resolved. -- http://www.catb.org/~esr/";>Eric S. Raymond My work is funded by the Internet Civil Engineering Institute: https://icei.org Please visit their site and donate: the civilization you save might be your own.
Re: So what's the status of the Git migration?
On Thu, 17 May 2018, Richard Earnshaw (lists) wrote: > Another year; another release; and still no sign of progress on the git > migration. > > Any ideas on how much longer this is going to take? See git://thyrsus.com/repositories/gcc-conversion.git for the current version of the conversion machinery, including a TODO list (and see also http://esr.ibiblio.org/?p=7959 ). Presumably required work on the GCC side (deciding appropriate policies on branch deletion / non-fast-forward pushes, developing hooks / repository configuration to implement those policies and send commit mails, writing updates to documentation and scripts) could be done in parallel with the conversion work, but Jason may already have some of that done anyway. -- Joseph S. Myers jos...@codesourcery.com
