On Sat, May 02, 2020 at 09:53:49PM +0200, Paul Gevers wrote:
>...
> 3) In the current state, I think it boils down to the question if armel
> and mipsel should be dropped for bullseye or not. What do we think
> ourselves? Myself, I've been regularly cursing mipsel for it being so
> much slower to b
On 2020-05-15 08:23, YunQiang Su wrote:
> Matthias Klose 于2020年5月14日周四 下午11:45写道：
> >
> > On 5/7/20 9:41 PM, Paul Gevers wrote:
> > > Hi
> > >
> > > On 02-05-2020 21:53, Paul Gevers wrote:
> > >> I don't think anybody likes to do it, but we have to discuss the
> > >> architectures that will be par
Matthias Klose 于2020年5月14日周四 下午11:45写道：
>
> On 5/7/20 9:41 PM, Paul Gevers wrote:
> > Hi
> >
> > On 02-05-2020 21:53, Paul Gevers wrote:
> >> I don't think anybody likes to do it, but we have to discuss the
> >> architectures that will be part of bullseye. In the before last IRC
> >> meeting I pro
On 5/7/20 9:41 PM, Paul Gevers wrote:
> Hi
>
> On 02-05-2020 21:53, Paul Gevers wrote:
>> I don't think anybody likes to do it, but we have to discuss the
>> architectures that will be part of bullseye. In the before last IRC
>> meeting I promised I would send this mail, so here we go. Let's see w
Hi
On 02-05-2020 21:53, Paul Gevers wrote:
> I don't think anybody likes to do it, but we have to discuss the
> architectures that will be part of bullseye. In the before last IRC
> meeting I promised I would send this mail, so here we go. Let's see what
> items we consider a must. Anybody else th
Dear all,
I don't think anybody likes to do it, but we have to discuss the
architectures that will be part of bullseye. In the before last IRC
meeting I promised I would send this mail, so here we go. Let's see what
items we consider a must. Anybody else that wants to step in, feel free
to take an
6 matches
Mail list logo
