From: Andy Wingo <wingo@pobox.com>
To: Freja Nordsiek <fnordsie@gmail.com>
Cc: 24657-done@debbugs.gnu.org
Subject: bug#24657: Autoconf macro GUILE_PROGS only looks for guile without version suffix even if given version - patch included
Date: Tue, 14 Mar 2017 15:44:13 +0100 [thread overview]
Message-ID: <87lgs77waq.fsf@pobox.com> (raw)
In-Reply-To: <CAOqf98ousRjj=mmP-mvmytq-YxWXyvwhN-KzoORQMrstWiK+Kg@mail.gmail.com> (Freja Nordsiek's message of "Tue, 14 Mar 2017 15:25:42 +0100")
On Tue 14 Mar 2017 15:25, Freja Nordsiek <fnordsie@gmail.com> writes:
> Found a bug in the modifications you made. Sorry for not catching this
> before it got included into the Guile 2.1.8 release.
Thank you! Applied. Note that in the gnu coding standards you need an
entry in the commit log for every file you modify. Blah, I know, but
that's how it is.
Andy
prev parent reply other threads:[~2017-03-14 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 9:45 bug#24657: Autoconf macro GUILE_PROGS only looks for guile without version suffix even if given version - patch included Freja Nordsiek
2017-02-23 9:43 ` Andy Wingo
2017-02-23 22:31 ` Freja Nordsiek
2017-03-14 14:25 ` Freja Nordsiek
2017-03-14 14:44 ` 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=87lgs77waq.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=24657-done@debbugs.gnu.org \
--cc=fnordsie@gmail.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).