On 11/14/22 14:06, Gerald Pfeifer wrote:
> On Mon, 14 Nov 2022, Martin Liška wrote:
>> The situation with the Sphinx migration went out of control. The TODO
>> list overwhelmed me and there are road-blocks that can't be easily fixed
>> with what Sphinx currently supports.
>
> This migration
On Mon, 14 Nov 2022, Jonathan Wakely wrote:
> I formatted my new region/endregion pragmas on one line because that
> seemed to be how it should be done for rSt, e.g. we had:
>
> ``#pragma GCC push_options`` ``#pragma GCC pop_options``
>
> But I think the attached patch is more correct for how we
On Mon, 14 Nov 2022, Martin Liška wrote:
> The situation with the Sphinx migration went out of control. The TODO
> list overwhelmed me and there are road-blocks that can't be easily fixed
> with what Sphinx currently supports.
This migration was/is a huge and complex undertaking, and you have
On Mon, 14 Nov 2022 at 08:40, Martin Liška wrote:
>
> On 11/14/22 03:49, Martin Liška wrote:
> > I'm going to revert the patchset during today (Monday) and I'll send a
> > patch with a couple
> > of new changes that landed in the period of time we used Sphinx.
>
> The revert is done and I
On 11/14/22 03:49, Martin Liška wrote:
> I'm going to revert the patchset during today (Monday) and I'll send a patch
> with a couple
> of new changes that landed in the period of time we used Sphinx.
The revert is done and I included ce51e8439a491910348a1c5aea43b55f000ba8ac
commit
that ports
Hi.
The situation with the Sphinx migration went out of control. The TODO list
overwhelmed me and there are road-blocks that can't be easily fixed with what
Sphinx currently supports. That would require addition of an upstream support
and
a possible new Sphinx release.
Let me summarize the
