From: Jan Nieuwenhuizen <janneke@gnu.org>
To: 33216@debbugs.gnu.org
Subject: bug#33216: using custom optimization options eats goops object
Date: Wed, 31 Oct 2018 17:28:23 +0100 [thread overview]
Message-ID: <87h8h2rsgo.fsf@gnu.org> (raw)
In-Reply-To: <877ehyrwy4.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Wed, 31 Oct 2018 15:51:31 +0100")
Jan Nieuwenhuizen <janneke@gnu.org> writes:
I get the same with latest stable-2.2
commit d9af6706e8a1a0148d492b222758e49e03d225b7
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2018-10-31 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 14:51 bug#33216: using custom optimization options eats goops object Jan Nieuwenhuizen
2018-10-31 16:28 ` Jan Nieuwenhuizen [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8h2rsgo.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=33216@debbugs.gnu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).