From: Paul Eggert <eggert@cs.ucla.edu>
To: bug-gnulib@gnu.org
Subject: Re: gc: fix configuration with --with-libgcrypt
Date: Sat, 24 Aug 2019 17:25:42 -0700 [thread overview]
Message-ID: <ad6363f8-8498-a386-379e-a88e64abef87@cs.ucla.edu> (raw)
In-Reply-To: <3314630.5BeXcWR3dH@omega>
Bruno Haible wrote:
> Paul and Karl: If you agree, can we add a $LIBGCRYPT to config/srclist.txt?
We like keeping files in sync; that's what config/srclist.txt is for. So I'm all
for this, and expect Karl will be too.
next prev parent reply other threads:[~2019-08-25 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 9:12 gc: fix configuration with --with-libgcrypt Bruno Haible
2019-08-25 0:25 ` Paul Eggert [this message]
2019-11-18 12:10 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad6363f8-8498-a386-379e-a88e64abef87@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@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).