From: "Eric S. Raymond" <esr@thyrsus.com>
To: Jeff Law <law@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Reposurgeon status
Date: Thu, 26 Sep 2019 18:02:00 -0000 [thread overview]
Message-ID: <20190926180157.GB39494@thyrsus.com> (raw)
In-Reply-To: <769e5710-8d0a-9953-4d40-7ddf3370ab06@redhat.com>
Jeff Law <law@redhat.com>:
> 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.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2019-09-26 18:02 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
2019-09-26 18:02 ` Eric S. Raymond [this message]
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=20190926180157.GB39494@thyrsus.com \
--to=esr@thyrsus.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
/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).