From: Eli Zaretskii <eliz@gnu.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: 13734@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#13734: 24.3.50; ../src/lisp.h:2485:10: error: address expression must be an lvalue or a function designator
Date: Sat, 02 Mar 2013 19:01:13 +0200 [thread overview]
Message-ID: <83y5e5u46e.fsf@gnu.org> (raw)
In-Reply-To: <CF72166B-867B-4C12-9BCC-CC6AD70CAD6F@Freenet.DE>
> From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
> Date: Sat, 2 Mar 2013 17:26:21 +0100
> Cc: schwab@linux-m68k.org,
> 13734@debbugs.gnu.org
>
> Your fix was fetched by bzr:
>
> revno: 111912
> behebt den Fehler: http://debbugs.gnu.org/13734
> committer: Eli Zaretskii <eliz@gnu.org>
> branch nick: trunk
> timestamp: Sat 2013-03-02 10:19:45 +0200
> message:
> Fix bug #13734 with errors in lisp.h macro expansion.
>
> src/lisp.h (XPNTR) [!USE_LSB_TAG]: Fix parentheses nesting.
>
> …but not applied? See the file's date from thursday:
>
> -rw-r--r-- 1 pete admin 137928 28. Feb 23:27 src/lisp.h
See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13734#49.
next prev parent reply other threads:[~2013-03-02 17:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 11:48 bug#13734: 24.3.50; ../src/lisp.h:2485:10: error: address expression must be an lvalue or a function designator Peter Dyballa
2013-02-17 13:19 ` Andreas Schwab
2013-02-17 16:10 ` Peter Dyballa
2013-02-17 16:16 ` Andreas Schwab
2013-02-17 16:31 ` Peter Dyballa
2013-03-01 19:13 ` Peter Dyballa
2013-03-01 19:45 ` Glenn Morris
2013-03-01 20:06 ` Peter Dyballa
2013-03-01 20:27 ` Eli Zaretskii
2013-03-01 23:25 ` Peter Dyballa
2013-03-02 7:58 ` Andreas Schwab
2013-03-02 8:24 ` Eli Zaretskii
2013-03-02 8:39 ` Eli Zaretskii
2013-03-02 9:06 ` Eli Zaretskii
2013-03-02 16:26 ` Peter Dyballa
2013-03-02 17:01 ` Eli Zaretskii [this message]
2013-02-17 16:15 ` Peter Dyballa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y5e5u46e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13734@debbugs.gnu.org \
--cc=Peter_Dyballa@Freenet.DE \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.