Re: [pretest] emacs-26.0.90

2017-11-09 Thread Grégoire Jadi
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

Re: [pretest] emacs-26.0.90

2017-11-06 Thread Grégoire Jadi
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

Re: [pretest] emacs-26.0.90

2017-11-06 Thread Jeremie Courreges-Anglas
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

Re: [pretest] emacs-26.0.90

2017-11-06 Thread Grégoire Jadi
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).

Re: [pretest] emacs-26.0.90

2017-11-05 Thread Piotr Isajew
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

Re: [pretest] emacs-26.0.90

2017-10-29 Thread Grégoire Jadi
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

Re: [pretest] emacs-26.0.90

2017-10-27 Thread Jeremie Courreges-Anglas
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

Re: [pretest] emacs-26.0.90

2017-10-26 Thread Jeremie Courreges-Anglas
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

Re: [pretest] emacs-26.0.90

2017-10-25 Thread Jeremie Courreges-Anglas
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

Re: [pretest] emacs-26.0.90

2017-10-18 Thread Manuel Giraud
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

Re: [pretest] emacs-26.0.90

2017-10-17 Thread Sunil Nimmagadda
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