From: "Ludovic Courtès" <INVALID.NOREPLY@gnu.org>
To: ludo@gnu.org, dalepsmith@gmail.com, 9835@debbugs.gnu.org
Subject: bug#9835: [bug #32515] Manual needs to document extensiondir and sitedir pkg-config variables
Date: Sat, 22 Oct 2011 14:20:01 +0000 [thread overview]
Message-ID: <20111022-142001.sv15145.9975@savannah.gnu.org> (raw)
In-Reply-To: <20110217-150955.sv3562.65682@savannah.gnu.org>
Update of bug #32515 (project guile):
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
I think commit fe4ea6859e7d19a0fe2694a3fb49f4abb722afc1 addresses most of your
concerns. Thanks!
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?32515>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2011-10-22 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 15:09 [bug #32515] Manual needs to document extensiondir and sitedir pkg-config variables Dale P. Smith
2011-10-22 14:20 ` Ludovic Courtès [this message]
2011-10-22 15:59 ` bug#9835: " Ludovic Courtès
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=20111022-142001.sv15145.9975@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=9835@debbugs.gnu.org \
--cc=dalepsmith@gmail.com \
--cc=ludo@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).