Piotr Isajew writes:
> On Mon, Nov 06, 2017 at 03:24:38PM +0100, Grégoire Jadi wrote:
>
>> Jeremie Courreges-Anglas writes:
>>
>> > Very interesting, thanks to both of you for your reports and
>> > investigations. I've never hit this, probably because I run the no_x11
>> > flavor. I'll see wh
Jeremie Courreges-Anglas writes:
> Very interesting, thanks to both of you for your reports and
> investigations. I've never hit this, probably because I run the no_x11
> flavor. I'll see what I can do to get this fixed, but if someone (tm)
> affected can file a bugreport upstream, that would b
On Mon, Nov 06 2017, gj...@omecha.info (Grégoire Jadi) wrote:
> Piotr Isajew writes:
>
>> Dnia 15.10.2017 Jeremie Courreges-Anglas napisał/a:
>>>
>>> Here's a diff for the first pretest in the emacs-26 release cycle.
>>> Among other things, emacs now uses system malloc(3) at runtime (gmalloc
>>>
Piotr Isajew writes:
> Dnia 15.10.2017 Jeremie Courreges-Anglas napisał/a:
>>
>> Here's a diff for the first pretest in the emacs-26 release cycle.
>> Among other things, emacs now uses system malloc(3) at runtime (gmalloc
>> is still used at build/unexec time).
>>
>> As usual build & test repor
Dnia 15.10.2017 Jeremie Courreges-Anglas napisał/a:
>
> Here's a diff for the first pretest in the emacs-26 release cycle.
> Among other things, emacs now uses system malloc(3) at runtime (gmalloc
> is still used at build/unexec time).
>
> As usual build & test reports are welcome, especially if y
Jeremie Courreges-Anglas writes:
> On Thu, Oct 26 2017, Jeremie Courreges-Anglas wrote:
>> On Wed, Oct 25 2017, Jeremie Courreges-Anglas wrote:
>>> On Sun, Oct 15 2017, Jeremie Courreges-Anglas wrote:
Here's a diff for the first pretest in the emacs-26 release cycle.
Among other thin
On Thu, Oct 26 2017, Jeremie Courreges-Anglas wrote:
> On Wed, Oct 25 2017, Jeremie Courreges-Anglas wrote:
>> On Sun, Oct 15 2017, Jeremie Courreges-Anglas wrote:
>>> Here's a diff for the first pretest in the emacs-26 release cycle.
>>> Among other things, emacs now uses system malloc(3) at ru
On Wed, Oct 25 2017, Jeremie Courreges-Anglas wrote:
> On Sun, Oct 15 2017, Jeremie Courreges-Anglas wrote:
>> Here's a diff for the first pretest in the emacs-26 release cycle.
>> Among other things, emacs now uses system malloc(3) at runtime (gmalloc
>> is still used at build/unexec time).
>>
>
On Sun, Oct 15 2017, Jeremie Courreges-Anglas wrote:
> Here's a diff for the first pretest in the emacs-26 release cycle.
> Among other things, emacs now uses system malloc(3) at runtime (gmalloc
> is still used at build/unexec time).
>
> As usual build & test reports are welcome, especially if yo
Jeremie Courreges-Anglas writes:
> Here's a diff for the first pretest in the emacs-26 release cycle.
> Among other things, emacs now uses system malloc(3) at runtime (gmalloc
> is still used at build/unexec time).
>
> As usual build & test reports are welcome, especially if you use an arch
> dif
Jeremie Courreges-Anglas writes:
> Here's a diff for the first pretest in the emacs-26 release cycle.
> Among other things, emacs now uses system malloc(3) at runtime (gmalloc
> is still used at build/unexec time).
>
> As usual build & test reports are welcome, especially if you use an arch
> di
Here's a diff for the first pretest in the emacs-26 release cycle.
Among other things, emacs now uses system malloc(3) at runtime (gmalloc
is still used at build/unexec time).
As usual build & test reports are welcome, especially if you use an arch
different from amd64 / arm, or if you use one of
12 matches
Mail list logo