From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>
Cc: Gnulib bugs <bug-gnulib@gnu.org>
Subject: Re: [PATCH] crypto: add missing file af_alg.h
Date: Tue, 7 Sep 2021 14:51:38 -0700 [thread overview]
Message-ID: <ebb21138-79ce-8f45-cda7-e34a24264d3c@cs.ucla.edu> (raw)
In-Reply-To: <7210319.jCCqRG4XHG@omega>
On 9/7/21 11:15 AM, Bruno Haible wrote:
> This looks unnecessary to me.
Oh, you're right. I got confused by a recent attempt of mine to merge
recent Gnulib into Emacs. Emacs avoids some modules, which led to
af_alg.h going missing there, and I thought this was a Gnulib problem.
I will fix the problem on the Emacs side, and have reverted the Gnulib
patch. Thanks for reporting the problem.
next prev parent reply other threads:[~2021-09-07 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 1:44 [PATCH] crypto: add missing file af_alg.h Paul Eggert
2021-09-07 18:15 ` Bruno Haible
2021-09-07 21:51 ` Paul Eggert [this message]
2021-09-07 23:23 ` Bruno Haible
2021-09-08 0:12 ` Paul Eggert
2021-09-19 0:02 ` crypto digests modules restructuring Bruno Haible
2021-09-19 13:20 ` Improve 'configure --help' output for crypto modules 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=ebb21138-79ce-8f45-cda7-e34a24264d3c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--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).