[debbugs-tracker] bug#16487: closed (emacs source and a particular commit)

[GNU bug Tracking System]

Your message dated Sun, 19 Jan 2014 00:16:10 +0100
with message-id <address@hidden>
and subject line Re: bug#16487: please delete this bug!
has caused the debbugs.gnu.org bug report #16487,
regarding emacs source and a particular commit
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
16487: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16487
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> emacs source and a particular commit
>
>
>
>
> Date: 
>
> Sat, 18 Jan 2014 21:09:40 +0000
>
>
>
>
> I was recently involved in a discussion entitled:
>
>         bug#15946: 24.3; Mac OS X, Mavericks, distnoted process
>
> From this I learned that there are nightlies available from emacsformacosx.com 
> and I was able to download one and discover that the memory leak has been fixed.
>
> Unfortunately I discovered that emacs has changed a lot and in particular I am 
> unable to use nxhtml and mumamo packages to edit JavaScript inside a django 
> template anymore. One error after another. Clearly some LISP apis have changed.
>
> So what I want to do is find the fix for the memory leak and apply it to emacs 
> 24.3.1 so I can have my memory leak fix without losing functionality I cannot 
> live without.
>
> So does anybody have any advice? I have cloned a git repository from here:
>
>         http://savannah.gnu.org/git/?group=emacs
>
> but searching the commits and tags has not yielded 24.3.1 for me. When was 
> 24.3.1 released?
>
> Once I get THAT commit I need to find the other one with the macosx fix that 
> was blowing up both emacs AND distnoted.
>
> Thanks.
>
> JP
>
>
>
>
> --- End Message ---

--- Begin Message --- Subject: Re: bug#16487: please delete this bug! Date: Sun, 19 Jan 2014 00:16:10 +0100

2014/1/18 Jonathan Payne <address@hidden>

I was horrible confused about this list. I sent a non-bug report to this alias and am horribly embarrassed.

Please delete if possible.

Hi,

Just reply to address@hidden with the reasons for bug closing as I am doing now and bug report will be automatically closed. You should receive the closing report short after this email.

 

Regards,

--

Agustin

--- End Message ---