public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: esr@thyrsus.com, gcc@gcc.gnu.org
Subject: Re: Reposurgeon status
Date: Thu, 26 Sep 2019 15:30:00 -0000	[thread overview]
Message-ID: <769e5710-8d0a-9953-4d40-7ddf3370ab06@redhat.com> (raw)
In-Reply-To: <20190925203218.GA43287@thyrsus.com>

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

  reply	other threads:[~2019-09-26 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 20:32 Eric S. Raymond
2019-09-26 15:30 ` Jeff Law [this message]
2019-09-26 18:02   ` Eric S. Raymond
2019-09-26 19:39     ` Joseph Myers
2019-09-26 20:13       ` Eric S. Raymond

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=769e5710-8d0a-9953-4d40-7ddf3370ab06@redhat.com \
    --to=law@redhat.com \
    --cc=esr@thyrsus.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).