From: Andy Wingo <wingo@pobox.com>
To: Matt Wette <matthew.wette@verizon.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 21698@debbugs.gnu.org
Subject: bug#21698: accessing multiple flagged values with (ice-9 getopt-long)
Date: Sat, 25 Jun 2016 10:07:01 +0200 [thread overview]
Message-ID: <8737o1d74q.fsf@pobox.com> (raw)
In-Reply-To: <34B3FA9E-EDD5-492B-8473-CEAF770E1241@verizon.net> (Matt Wette's message of "Fri, 24 Jun 2016 17:12:06 -0700")
On Sat 25 Jun 2016 02:12, Matt Wette <matthew.wette@verizon.net> writes:
> Could you at the least add a reference to SRFI-37 in the section on
> (ice-9 getopt-long), in case you don’t go further — e.g., replace it?
Done (in master, will backport later).
Andy
prev parent reply other threads:[~2016-06-25 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 17:05 bug#21698: accessing multiple flagged values with (ice-9 getopt-long) Matt Wette
2016-06-24 14:53 ` Andy Wingo
2016-06-24 15:21 ` Matt Wette
2016-06-24 15:30 ` Ludovic Courtès
2016-06-24 17:14 ` Andy Wingo
2016-06-25 0:12 ` Matt Wette
2016-06-25 8:07 ` Andy Wingo [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=8737o1d74q.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=21698@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=matthew.wette@verizon.net \
/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).