From: Bruce Korb <bkorb@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: deprecated features
Date: Tue, 23 Jan 2007 16:10:10 -0800 [thread overview]
Message-ID: <45B6A3E2.7070704@gnu.org> (raw)
In-Reply-To: <45B6AC0B.9030108@xs4all.nl>
Han-Wen Nienhuys wrote:
>>>> By the way, have you all given any consideration to releasing a
>>>> valgrind config file that would clean out valgrind chaff?
>>> I always use the file below. I am not sure what the best way to
>>> distribute it would be.
>> I think there are two reasonable ways:
>>
>> 1. on the web site and referenced in the docs that it lives there
>> 2. stash in the datadir and make it obtainable via:
>>
>> $ cp `guile-config datadir`/guile.supp $my_debug_dir
>
> Actually, I think it makes more sense to submit it to the valgrind guys.
Trouble is that it is Guile-version dependent. You cannot sync
your releases. It should come from Guile. :) (My opinions are
not overly humble...) I prefer method #2, but either of these
works for me. Cheers - Bruce
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-01-24 0:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 15:24 Eval options macro: backward compatibility? Han-Wen Nienhuys
2007-01-20 14:35 ` Ludovic Courtès
2007-01-22 14:18 ` Han-Wen Nienhuys
2007-01-22 20:48 ` Kevin Ryde
2007-01-23 0:51 ` deprecated features Han-Wen Nienhuys
2007-01-23 1:03 ` Kevin Ryde
2007-01-23 1:20 ` Han-Wen Nienhuys
2007-01-23 14:50 ` Bruce Korb
2007-01-23 22:45 ` Han-Wen Nienhuys
2007-01-23 23:20 ` Bruce Korb
2007-01-24 0:44 ` Han-Wen Nienhuys
2007-01-24 0:10 ` Bruce Korb [this message]
2007-01-23 23:10 ` Han-Wen Nienhuys
2007-01-23 23:35 ` Bruce Korb
2007-01-24 0:38 ` Han-Wen Nienhuys
2007-01-24 22:44 ` Kevin Ryde
2007-01-22 15:28 ` Eval options macro: backward compatibility? Han-Wen Nienhuys
2007-01-22 20:50 ` Kevin Ryde
2007-01-24 21:05 ` Kevin Ryde
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=45B6A3E2.7070704@gnu.org \
--to=bkorb@gnu.org \
--cc=guile-devel@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).