(For alsa-de...@alsa-project.org I’ve attached the diffs this
eMail thread has been about, with hope you will apply them in
the next upstream release.)
Elimar Riesebieter dixit:
>it seems that you are an exclusive user of the x32 port ;-) Please
If you actually read that thread you’d know I’m n
Hi Thorsten,
* Thorsten Glaser [2017-08-01 18:18 +0200]:
> Source: alsa-lib
> Version: 1.1.3-5
> Severity: important
> Tags: patch
>
> I was a bit annoyed I could not play any sound on my x32 desktop
> any more and today investigated it. It boils down to that amd64
> assembly code was run, whic
On Wed, 12 Dec 2018, Elimar Riesebieter wrote:
> Why don't you try to push your patches upstream? I won't because you
Because I don’t even *know* upstream, let alone have a
working relationship with them.
> are the author and you know what you did.
☹
bye,
//mirabilos
--
tarent solutions GmbH
* Thorsten Glaser [2018-12-10 18:18 +0100]:
> found 870396 1.1.7-1
> thanks
>
> Here is an updated debdiff, as usual. It still fixes the segfaults.
Why don't you try to push your patches upstream? I won't because you
are the author and you know what you did.
Elimar
--
On the keyboard of lif
Hi,
>As I can't evaluate the impact to our officially supported arch's I
The impact of 0011-distinguish-x32-from-amd64.patch on any other
architecture is absolutely zero, and that’s what fixes x32, so…
>and wait till they be pushed.
… I’d prefer it very much if you can merge at least that one.
Hi Thorsten,
* Thorsten Glaser [2017-08-01 18:18 +0200]:
> Source: alsa-lib
> Version: 1.1.3-5
> Severity: important
> Tags: patch
>
> I was a bit annoyed I could not play any sound on my x32 desktop
> any more and today investigated it. It boils down to that amd64
> assembly code was run, whic
6 matches
Mail list logo
