Re: HyperKitty: Thread tree broken?

2023-01-12 Thread Kevin Fenzi
On Thu, Jan 12, 2023 at 07:14:33PM +0100, Jun Aruga (he / him) wrote: > > > > 1. > > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#QZUTH6DSULKYBMGPPYNZMPX7YSYKOBTT > > > > 2. > > > >

Re: HyperKitty: Thread tree broken?

2023-01-12 Thread Jun Aruga (he / him)
> > > 1. > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#QZUTH6DSULKYBMGPPYNZMPX7YSYKOBTT > > > 2. > > >

Re: HyperKitty: Thread tree broken?

2023-01-12 Thread Kevin Fenzi
On Thu, Jan 12, 2023 at 11:41:20AM -0500, Stephen Smoogen wrote: > On Thu, 12 Jan 2023 at 11:34, Jun Aruga (he / him) > wrote: > > > I see one issue on HyperKitty on the Fedora project. > > > > Below is thread 1 and 2 for the actual thread: "RISC-V -- are we ready > > for more, and what do we

Re: HyperKitty: Thread tree broken?

2023-01-12 Thread Stephen Smoogen
On Thu, 12 Jan 2023 at 11:34, Jun Aruga (he / him) wrote: > I see one issue on HyperKitty on the Fedora project. > > Below is thread 1 and 2 for the actual thread: "RISC-V -- are we ready > for more, and what do we need to do it?" Do you know why it's not one > thread page? > > 1. >

HyperKitty: Thread tree broken?

2023-01-12 Thread Jun Aruga (he / him)
I see one issue on HyperKitty on the Fedora project. Below is thread 1 and 2 for the actual thread: "RISC-V -- are we ready for more, and what do we need to do it?" Do you know why it's not one thread page? 1.