Re: Reposurgeon status
Joseph Myers : > On Thu, 26 Sep 2019, Eric S. Raymond wrote: > > > > You might want to update the state of reposurgeon on that page. > > > > I will do so. > > Note that once you've created an account, someone will need to add it to > the EditorGroup page before you can edit. I'm having trouble with basic account creation, actually. It's to all appearances not accepting the password I set up. I have sent a reset request. -- http://www.catb.org/~esr/";>Eric S. Raymond
Re: Reposurgeon status
On Thu, 26 Sep 2019, Eric S. Raymond wrote: > > You might want to update the state of reposurgeon on that page. > > I will do so. Note that once you've created an account, someone will need to add it to the EditorGroup page before you can edit. -- Joseph S. Myers jos...@codesourcery.com
Re: Reposurgeon status
Jeff Law : > Probably the most important thing to know is the project will make a > decision on Dec 16 to choose the conversion tool. The evaluation is > based on the state of tool's conversion on that date. More details: > > > https://gcc.gnu.org/wiki/GitConversion > > You should consider the dates in there as firm. I think it is extremely likely that I will have a final conversion ready by then. The only known problem that is in any way serious is the x-bit propagation bug, and I may already have fixed that. I'd think I'd have to get blindsided by something much larger to miss that deadline. > You might want to update the state of reposurgeon on that page. I will do so. -- http://www.catb.org/~esr/";>Eric S. Raymond
Re: Reposurgeon status
On 9/25/19 2:32 PM, Eric S. Raymond wrote: > Since the subject of repository conversions has come up, a situation report... > > I am in the very last stages of qualifying the Go port of reposurgeon. > Most importantly to your project, the Go code passed all of the > existing regression tests for reading Subversion stream dumps two days > ago. That is a big deal, as the stream dump reader was by *far* the > trickiest and most bug-prone part to translate. [ ... ] > > I think I'm looking at somewhere between 7 and 14 days until I can start > work on the GCC move again. Getting to this point has taken a year. [ ... ] Good to hear there's been major progress. Probably the most important thing to know is the project will make a decision on Dec 16 to choose the conversion tool. The evaluation is based on the state of tool's conversion on that date. More details: > https://gcc.gnu.org/wiki/GitConversion You should consider the dates in there as firm. You might want to update the state of reposurgeon on that page. Jeff
Reposurgeon status
Since the subject of repository conversions has come up, a situation report... I am in the very last stages of qualifying the Go port of reposurgeon. Most importantly to your project, the Go code passed all of the existing regression tests for reading Subversion stream dumps two days ago. That is a big deal, as the stream dump reader was by *far* the trickiest and most bug-prone part to translate. Am now working on debugging a fairly peripheral feature called the extractor harness. This is what you use when a VCS doesn't have a stream dump format and you have to call its CLI and mine the reports from the CLI tools to get out the conyent and metadata. Not needed for the GCC move. The main application for it is actually lifting Mercurial repositories - their export tools are weak and poorly supported. After that I want to get topological sorting of commits working in Go. Also not needed for the GCC move, but I don't want to have any loose ends dangling when I dive back into that. Third and last item, clearing my current bug list. The big one is that last time I looked there was something wrong near execute-bit propagation in interpreting Subversion dumps. But it is actually possible that I've already fixed this in passing while verifying the port - I found a suspicious failure to distinguish between "no property set" and "an empty property set" last week. I think I'm looking at somewhere between 7 and 14 days until I can start work on the GCC move again. Getting to this point has taken a year. However, the hopes of a big speedup look like they'll be borne out. Preliminary indications are that my test runs will be at least 12x faster. In part due to Go and in part due to a new Great Beast, a 16-core Threadripper machine with 128GB ram. Finishing the move should now be within the realm of the practically achievable. -- http://www.catb.org/~esr/";>Eric S. Raymond
