Richard Earnshaw (lists) :
> > No, I was thinking more of rearnsha bailing out to handle a family emergency
> > and muttering something about not being back for a couple of weeks. If
> > that's
> > been resolved I haven't heard about it.
>
> I don't think that should affect things, as I think Jos
On 19/12/2019 16:00, Eric S. Raymond wrote:
Joseph Myers :
On Thu, 19 Dec 2019, Eric S. Raymond wrote:
There are other problems that might cause a delay beyond the
31st, however. Best if I let Joseph nd Richard explain those.
I presume that's referring to the checkme: bug annotations where t
Joseph Myers :
> On Thu, 19 Dec 2019, Eric S. Raymond wrote:
>
> > There are other problems that might cause a delay beyond the
> > 31st, however. Best if I let Joseph nd Richard explain those.
>
> I presume that's referring to the checkme: bug annotations where the PR
> numbers in commit messag
On Thu, 19 Dec 2019, Eric S. Raymond wrote:
> There are other problems that might cause a delay beyond the
> 31st, however. Best if I let Joseph nd Richard explain those.
I presume that's referring to the checkme: bug annotations where the PR
numbers in commit messages seem suspicious. I don't
Mark Wielaard :
> Do we already have a new date for when we are making that decision?
I believe Joseph was planning on Dec 31st.
My team's part will be ready - the enabling reposurgeon changes should
done in a week or so, with most of that being RFEs that could be
dropped if there were real time
Hi,
On Wed, 2019-12-18 at 21:55 +, Joseph Myers wrote:
> On Tue, 17 Dec 2019, Joseph Myers wrote:
> > I've made test conversions of the GCC repository with reposurgeon
> > available (gcc.gnu.org / sourceware.org account required to access
> > these git+ssh repositories, it doesn't need to be o
