Vít Ondruch wrote:
> Shouldn't be the feature page just deleted? Or archived in some better
> category such as "deferred"? There is 256 (nice number ;) incomplete
> feature pages, some of them are probably abandoned as this one. Would be
> nice to do some cleanup there, to see what is actively work
On 1/17/13 2:16 PM, Adam Tkac wrote:
Ok, I'm going to switch libjpeg-turbo-jpeg8-ABI to incomplete category,
thanks.
Shouldn't be the feature page just deleted? Or archived in some
better category such as "deferred"? There is 256 (nice number ;)
incomplete feature pages, some of them are probabl
On Thu, Jan 17, 2013 at 12:37:56PM +0100, Vít Ondruch wrote:
> Dne 16.1.2013 17:42, Jaroslav Reznik napsal(a):
> >- Original Message -
> >>Hello all,
> >>
> >>after discussion with libjpeg and libjpeg-turbo upstreams I decided
> >>to drop the
> >>"jpeg8 API/ABI" feature and include only jpe
Dne 16.1.2013 17:42, Jaroslav Reznik napsal(a):
- Original Message -
Hello all,
after discussion with libjpeg and libjpeg-turbo upstreams I decided
to drop the
"jpeg8 API/ABI" feature and include only jpeg6 API/ABI.
Ok, I'm going to switch libjpeg-turbo-jpeg8-ABI to incomplete category
On Wed, Jan 16, 2013 at 09:38:29AM -0700, Kevin Fenzi wrote:
> On Wed, 16 Jan 2013 17:14:26 +0100
> Adam Tkac wrote:
>
> > Hello all,
> >
> > after discussion with libjpeg and libjpeg-turbo upstreams I decided
> > to drop the "jpeg8 API/ABI" feature and include only jpeg6 API/ABI.
> > The main r
- Original Message -
> Hello all,
>
> after discussion with libjpeg and libjpeg-turbo upstreams I decided
> to drop the
> "jpeg8 API/ABI" feature and include only jpeg6 API/ABI.
Ok, I'm going to switch libjpeg-turbo-jpeg8-ABI to incomplete category,
thanks.
Jaroslav
> The main
> reason
On Wed, 16 Jan 2013 17:14:26 +0100
Adam Tkac wrote:
> Hello all,
>
> after discussion with libjpeg and libjpeg-turbo upstreams I decided
> to drop the "jpeg8 API/ABI" feature and include only jpeg6 API/ABI.
> The main reason is that libjpeg upstream didn't present any valid
> argument for post-j
Hello all,
after discussion with libjpeg and libjpeg-turbo upstreams I decided to drop the
"jpeg8 API/ABI" feature and include only jpeg6 API/ABI. The main reason is that
libjpeg upstream didn't present any valid argument for post-jpeg6 changes and
libjpeg-turbo is not going to port all post-jpeg6