From: Andy Wingo <INVALID.NOREPLY@gnu.org>
To: "Julian Graham" <julian.graham@aya.yale.edu>,
"Andy Wingo" <wingo@pobox.com>,
"Göran Weinholt" <goran@weinholt.se>,
bug-guile@gnu.org
Subject: [bug #31682] enum-set-union not working on defined enumerations
Date: Fri, 19 Nov 2010 16:11:13 +0000 [thread overview]
Message-ID: <20101119-161112.sv20118.68336@savannah.gnu.org> (raw)
In-Reply-To: <20101117-145842.sv2373.95924@savannah.gnu.org>
Update of bug #31682 (project guile):
Assigned to: None => juliang
_______________________________________________________
Follow-up Comment #1:
Julian has once again agreed to take a look. Thanks Julian! :)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?31682>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2010-11-19 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 13:58 [bug #31682] enum-set-union not working on defined enumerations Göran Weinholt
2010-11-19 16:11 ` Andy Wingo [this message]
2010-11-21 20:39 ` Julian Graham
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=20101119-161112.sv20118.68336@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=goran@weinholt.se \
--cc=julian.graham@aya.yale.edu \
--cc=wingo@pobox.com \
/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).