From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 31474@debbugs.gnu.org
Subject: bug#31474: logxor+ash trigger compilation bug?
Date: Mon, 28 May 2018 23:17:04 +0200 [thread overview]
Message-ID: <87bmczbhv3.fsf@gnu.org> (raw)
In-Reply-To: <87h8msxa16.fsf@netris.org> (Mark H. Weaver's message of "Mon, 28 May 2018 08:03:01 -0400")
Mark H Weaver writes:
> Here's an improved version of my patch. It's functionally equivalent
> but with more comprehensible code and more comments. I think this is
> ready to push to the stable-2.2 branch. Comments and suggestions
> welcome.
I tried it and it works for me. Thanks a lot!
Also, thanks for the workarounds you suggested, they indeed work without
this patch.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2018-05-28 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 18:16 bug#31474: logxor+ash trigger compilation bug? Jan Nieuwenhuizen
2018-05-28 2:13 ` Mark H Weaver
2018-05-28 12:03 ` Mark H Weaver
2018-05-28 21:17 ` Jan Nieuwenhuizen [this message]
2018-06-11 14:28 ` Mark H Weaver
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=87bmczbhv3.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=31474@debbugs.gnu.org \
--cc=mhw@netris.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).